When AT-TLS is enabled, some service homepage URLs don't work

Describe the bug
Enable AT-TLS for Zowe v3.3.0 with client.tls.attls and server.tls.attls both set to true, and a working AT-TLS configuration in the policy agent.

When browsing the API Catalog, services present their service home page as http://<host>:<port>/..., and clicking them loads a browser tab with an error (ERR_CONNECTION_RESET). I found Caching Service, Gateway, and ZSS all linked to an http endpoint, while API Catalog and App Server linked to https. z/OSMF was not AT-TLS enabled, and kept https.

I took a quick look at the discovery metadata, and homePageUrl for each service is set to http://. One oddity was App Server: the ZLUX service homePageUrl was http, but it still presented https in the API Catalog.

Steps to Reproduce

1. Enable AT-TLS with Zowe 3.3.0
2. Check the service homepage links in the API Catalog

Expected behavior
All service homepage links work

Details

• Version and build number: v3.x/staging, 3.3.10-SNAPSHOT
• Test environment: Marist 9,10,11

API Catalog Web UI (in case of API Catalog issue):

• OS: macOS
• Browser Chrome
• Version 139.0.7258.155 / arm64

Start by tracing how discovery metadata homePageUrl values are generated and displayed in the API Catalog when AT-TLS is enabled. Compare the links for Caching Service, Gateway, ZSS, API Catalog, App Server, and z/OSMF; done means all applicable service homepage links open successfully under the reported AT-TLS configuration.