fix: CORS Defaults v3

[pablocarle]

Description

Cherry pick of #4718

CORS behaviour:

CORS handling setting in Gateway (apiml.service.corsEnabled) means choosing whether the Gateway will use Gateway's defaults (false, default) OR taking the southbound's services metadata to override them (true)

When false (default) is used, only one path pattern matcher is created as /**

true creates specific path patterns (/gateway/** and service-specific ones) and provides either the same defaults as when CORS handling is disabled in Gateway OR the service-specified ones.

Type of change

• fix: Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud