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

In https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.7/html/clusters/cluster_mce_overview#hosted-control-planes-intro, before https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.7/html/clusters/cluster_mce_overview#hosting-service-cluster-configure-aws, we should add a section that explains the minimum required resources for each hosted cluster's control plane so that users can determine how many hypershift hosted clusters can fit into the MCE/ACM hub cluster. The content of this new section can be found here https://github.com/stolostron/hypershift-addon-operator/blob/main/docs/hcp_resource_minimum_reqs.md.

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

Provide info for the following steps:

1. - [x] Mandatory MCE 2.3

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

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

3. - [x] Mandatory for GA content:
            
       - [x] Add steps and/or other important conceptual information here: 
       

https://github.com/stolostron/hypershift-addon-operator/blob/main/docs/hcp_resource_minimum_reqs.md
            
       - [x] Add Required access level for the user to complete the task here:
       

MCE cluster admin

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

N/A
     
       - [x] Add link to dev story here: epic https://issues.redhat.com/browse/ACM-3343

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