WW-2963 default-action-ref fails to find wildcard named actions

[lukaszlenart]

Summary

Fixes WW-2963

• default-action-ref fallback now resolves via wildcard matching when the exact action map lookup fails
• Mirrors the exact→wildcard resolution pattern already used for request action names (3 lines added)
• Adds three tests covering exact-match default-action-ref, wildcard-match default-action-ref, and no-match fallback

Root Cause

In DefaultConfiguration.RuntimeConfigurationImpl.findActionConfigInNamespace(), the default-action-ref fallback only did actions.get(defaultActionRef) — an exact key lookup. If the default ref name (e.g., "movie-input") only matched a wildcard pattern (e.g., "movie-*"), the lookup returned null and the request failed with a 404.

Fix

After the exact lookup fails for the default action ref, also try the wildcard matcher:

config = actions.get(defaultActionRef);
if (config == null) {
    config = namespaceActionConfigMatchers.get(namespace).match(defaultActionRef);
}

Test plan

• ConfigurationTest#testDefaultActionRefWithWildcard — default-action-ref resolves via wildcard matching
• ConfigurationTest#testDefaultActionRefWithExactMatch — default-action-ref resolves via exact match (pre-existing behavior)
• ConfigurationTest#testDefaultActionRefWithWildcardNoMatch — returns null when default-action-ref matches neither
• Full ConfigurationTest suite passes with no regressions

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud