1. Proposed Title of this Feature Request

Display Custom API Server DNS Name for Hosted Clusters in ACM/MCE Console

2. What is the nature and description of the request?

This is a feature enhancement request for the Red Hat Advanced Cluster Management (ACM) and/or MultiCluster Engine (MCE) web console. Currently, when a user configures a custom API server DNS name and a corresponding TLS certificate for a HyperShift hosted cluster using the `HostedCluster` custom resource, the ACM/MCE web console only displays the original, default API server address.

This request proposes adding a new field or updating an existing field in the hosted cluster's overview page within the ACM/MCE web console to prominently display the custom API server DNS name. This would ensure that the console provides an accurate and complete picture of the cluster's configuration, reflecting the custom endpoint that users are expected to utilize.

apiVersion: hypershift.openshift.io/v1beta1
kind: HostedCluster
metadata:
  name: example-cluster
  namespace: clusters
spec:
  configuration:
    apiServer:
      servingCerts:
        namedCertificates:
        - names:
          - api-custom-cert-sample-hosted.sample-hosted.example.com
          servingCertificate:
            name: sample-hosted-kas-custom-cert
  kubeAPIServerDNSName: api-custom-cert-sample-hosted.sample-hosted.example.com

DOC: https://hypershift-docs.netlify.app/how-to/configure-ocp-components/custom-kas-kubeconfig/

3. Why does the customer need this? (List the business requirements here)
**

Improved User Experience for Console-Reliant Teams: Many administrators and developers rely heavily on the OpenShift Container Platform (OCP) and ACM/MCE web consoles as their primary interface for managing clusters. The absence of the custom API server DNS name in the console can lead to confusion and operational inefficiencies.

Enhanced Visibility and Awareness: By displaying the new custom API server DNS name, the console would make it immediately apparent to all users which endpoint should be used to access the hosted cluster. This reduces the need to inspect the `HostedCluster` custom resource YAML directly, saving time and effort.

Promotion of Secure Practices: The custom API server DNS name is often associated with a custom TLS certificate. Highlighting this custom endpoint in the UI reinforces the importance of using this secure and properly certificated address for all external communications with the hosted cluster.

Consistency Across Configuration and UI: The user interface should accurately reflect the underlying configuration of the resource. When a custom API server DNS is set in the `HostedCluster` CR, the ACM/MCE console should mirror this reality to provide a consistent and trustworthy management experience.

Reduced Support Overhead: Clear and accurate information in the UI can help prevent common user errors, such as attempting to use an outdated or incorrect API server address. This, in turn, can reduce the number of support requests related to connectivity and certificate issues for hosted clusters.

**
4. List any affected packages or components.

Red Hat Advanced Cluster Management (ACM) / MultiCluster Engine (MCE)