Information to document

Under https://github.com/stolostron/rhacm-docs/tree/2.10_stage/clusters/hosted_control_planes, we need to have a section to assist users what they things they can commonly override using `hcp create cluster` command such as setting the desired OCP release-image version.

These are the common settings for all supported infrastructure platforms and we can start elaborating on them and provide some examples first.

      --node-pool-replicas int32   If 0 or greater, creates a nodepool with that many replicas; else if less than 0, does not create a nodepool.
      --pull-secret string         File path to a pull secret.
      --release-image string       The OCP release image for the cluster. 

Take a look at https://issues.redhat.com/browse/ACM-10900. We also need to cover the upgrade path scenario in CLI. Add information on how to get the list of supported OCP versions and how to set the value for --release-image flag.

Also describe the upgrade scenarios with respect to local-cluster OCP version:

• Is there recommended upgrade order between local-cluster and hosted clusters?
• Is there any dependencies between local-cluster version and hosted clusters version?
• How independent are they?
• (Here is OCP hosted control plane doc https://docs.openshift.com/container-platform/4.15/hosted_control_planes/hcp-updating.html which points you to consider Kubernetes version skew which could be used to relate local-cluster to hosted clusters. )

In the HCP version upgrade section, we also need to include:

• https://github.com/openshift/hypershift/blob/main/docs/content/how-to/upgrades.md
• The workaround for https://issues.redhat.com/browse/ACM-13697 

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

Provide info for the following steps:

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

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

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

3. - [ ] Mandatory for GA content:
            
       - [ ] Add steps and/or other important conceptual information here: 
       
            
       - [ ] 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?)
     
     
       - [ ] Add link to dev story here:

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