Use production harbor for TKG Bom bits as defined in compatibility file

[jpmcb]

Bug Report

We need to use the production harbor for all future releases of TCE:

https://github.com/vmware-tanzu/community-edition/blob/main/Makefile#L57

this was a fast workaround to get us upgraded to the latest tanzu-framework version which does not have the latest compatible BOM artifacts from tanzu-framework release. For now, we can use the staging registry.

Expected Behavior

Use production harbor during build and release

Steps to Reproduce the Bug

When targeting the production harbor in our build:

$ CLUSTER_PLAN=dev tanzu management-cluster create mytest -i docker -v 10

Downloading TKG compatibility file from 'projects.registry.vmware.com/tkg/framework-zshippable/tkg-compatibility'
Error: unable to ensure prerequisites: unable to ensure tkg BOM file: failed to download default bom files from the registry: unable to get the default BOM file ImagePath and Image Tag from the TKG Compatibility file: unable to find the supported TKG BOM version for the management plugin version "v0.10.0" in the TKG Compatibility file "/home/ubuntu/.config/tanzu/tkg/compatibility/tkg-compatibility.yaml"

This is because the bom files are not present for the compatible version of tanzu-framework in the production harbor:

❯ cat ~/.config/tanzu/tkg/compatibility/tkg-compatibility.yaml
version: v20
managementClusterPluginVersions:
...
- version: v0.10.0
  supportedTKGBomVersions:
  - imagePath: tkg-bom
    tag: v1.5.0-tf-v0.10.0
...

❯ docker pull projects.registry.vmware.com/tkg/tkg-bom:v1.5.0-tf-v0.10.0
Error response from daemon: unknown: artifact tkg/tkg-bom:v1.5.0-tf-v0.10.0 not found

Screenshots or additional information and context

Related to #2523

Environment Details

N/a

Diagnostics and log bundle

N/a