Problem:
When an ODC environment is configured to use the ODC Cloud Connector, all REST integrations must use https://secure-gateway: as the base URL and pass the real target URL as a custom Host header. Since the secure gateway URL is the same across all environments, it adds no configuration value — yet it must be stored as a Setting, cluttering the Settings list with a technical implementation detail that developers never need to change.

Idea:
When the ODC Cloud Connector is active for an environment, ODC should recognize the Host header as the effective base URL for that integration and surface it in the Settings tab instead of (or in addition to) the raw base URL. This way, developers configure the meaningful value (the real target URL) and the platform handles the secure gateway routing transparently.

Benefits:

• Cleaner Settings list - no noise from gateway URLs that never change
• Easier onboarding - developers configure what they understand (the real API URL), not infrastructure details.
• Consistent with the spirit of Settings as environment-specific, meaningful configuration values.