[CAFV-464][1.3.z]Add suggested CRS labels to crs.yaml files

[rliang88]

Description

Please provide a brief description of the changes proposed in this Pull Request

Add these labels to all crs template files:

cluster-role.tkg.tanzu.vmware.com/management: ""
tanzuKubernetesRelease: ${TARGET_TANZUKUBERNETESRELEASE}
tkg.tanzu.vmware.com/cluster-name: ${CLUSTER_NAME}

Checklist

• tested locally
• updated any relevant dependencies
• updated any relevant documentation or examples

API Changes

Are there API changes?

• Yes
• No

If yes, please fill in the below

1. Updated conversions?
   • Yes
   • No
   • N/A
2. Updated CRDs?
   • Yes
   • No
   • N/A
3. Updated infrastructure-components.yaml?
   • Yes
   • No
   • N/A
4. Updated ./examples/capi-quickstart.yaml?
   • Yes
   • No
   • N/A
5. Updated necessary files under ./infrastructure-vcd/v1.0.0/?
   • Yes
   • No
   • N/A

Issue

If applicable, please reference the relevant issue

Fixes #

---

This change is 

[lzichong]

Reviewed 12 of 12 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @rliang88 and @sahithi)

---

templates/cluster-template-v1.20.8-crs.yaml line 11 at r1 (raw file):

    csi: external
    cluster-role.tkg.tanzu.vmware.com/management: ""
    tanzuKubernetesRelease: ${TARGET_TANZUKUBERNETESRELEASE}

Please check if clusterctl.yaml also needs to include TARGET_TANZUKUBERNETESRELEASE. When using clusterctl generate ..., it will look at clusterctl.yaml to set variables in the templates. Otherwise, if unset, it would give tanzuKubernetesRelease: "", if this is also okay we can move it as a optional field. Please double check this with @sahithi as well

otherwise.

[sahithi]

Sorry Richard, you did ask me whether to leave it empty and I said yes.
Can you please give a valid value so that users can see this as an example? See one of our RDEs that UI generates to see the format?