Change OpenAPI aggregation to use hardcoded clusters to add flexibility and resolve issue in Azure

[tjementum]

Summary & Motivation

Follow-up to the recent change for aggregating OpenAPI specifications. The aggregation was not working correctly in production because URLs for the self-contained systems were not fetched properly from the YARP configuration, leading to empty API contracts.

To resolve this, the list of YARP clusters to include in the aggregated OpenAPI specification is now hardcoded, rather than relying on conventions for clusters with an -api postfix. This adjustment provides more flexibility in configuring the setup.

Checklist

• [x] I have added a Label to the pull-request
• [x] I have added tests, and done manual regression tests
• [x] I have updated the documentation, if necessary

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[sonarcloud[bot]]

Please retry analysis of this Pull-Request directly on SonarCloud