Create an informative issue (See each section, incomplete templates/issues won't be triaged)

Using the current documentation as a model, please complete the issue template. 

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have

Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

 - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

 - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

Describe the changes in the doc and link to your dev story

Provide info for the following steps:

1. - [x] Mandatory Add the required version to the Fix version/s field.

2. - [x] Mandatory Choose the type of documentation change.

      - [ ] New topic in an existing section or new section
      - [x] Update to an existing topic

3. - [x] Mandatory for GA content:

• In ACM 2.9.0, submariner-addon is now deployed by the multiclusterhub-operator. Submariner is now a component that can be enabled/disabled by defauly when MCH is deployed onto the cluster. The submariner-addon will be deployed during the ACM installation, instead of being managed by the operator-lifecycle-manager (OLM).

       - [x] Add steps and/or other important conceptual information here: 

• When the user is ready to install ACM onto the cluster, they can create a MultiClusterHub CR and choose whether to enable/disable SubmarinerAddon.
• By default, SubmarinerAddon is enabled on the cluster.
• If the user decides to disable SubmarinerAddon, the submariner-addon pod will not be deployed onto the cluster.

       - [x] Add Required access level for the user to complete the task here:

• The user will need access/permission to update the MultiClusterHub CR to enable or disable the SubmarinerAddon within the cluster environment.
         

       - [x] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)

• The user can verify that the submariner-addon is being deployed by the multiclusterhub-operator by viewing the submariner-addon deployment's label in the open-cluster-management namespace. The labels will contain the following:

  labels:
    installer.name: multiclusterhub
    installer.namespace: open-cluster-management 

       - [x] Add link to dev story here: https://issues.redhat.com/browse/ACM-6913

4. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation: