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:
            
       - [x] Add steps and/or other important conceptual information here:

• In the https://github.com/stolostron/rhacm-docs/blob/2.9_stage/clusters/install_upgrade/adv_config_install.adoc doc, we need to add a table that contains the different component that MCE is deploying when installed. The table will provide a description and enabled field based on the default settings provided within MCE.

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

       -- [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)-
     
     
       - [x] Add link to dev story here: https://issues.redhat.com/browse/ACM-9483

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