tkgs tkc cluster creation failing when TKG_CUSTOM_IMAGE_REPOSITORY env variable has value

[chandrareddyp]

Bug description
the tanzu cluster create -f tkc.config --tkr v1.23.5---vmware.1-tkg.1-zshippable is failing for tkgs tkc cluster creation when environment variable TKG_CUSTOM_IMAGE_REPOSITORY is set with some value.
Affected product area (please put an X in all that apply)

• APIs
• Addons
• CLI
• Docs
• IAM
• Installation
• Plugin
• Security
• Test and Release
• User Experience

Expected behavior
should be able to create tkgs tkc cluster even when environment variable TKG_CUSTOM_IMAGE_REPOSITORY set with value
Steps to reproduce the bug
Build or install CLI, set environment variable TKG_CUSTOM_IMAGE_REPOSITORY with some value, then try tor create tkgs tkc cluster
Version (include the SHA if the version is not obvious)
❯ tanzu version
version: v0.25.0-dev
buildDate: 2022-07-15

Environment where the bug was observed (cloud, OS, etc)
mac os
Relevant Debug Output (Logs, manifests, etc)
❯ tanzu cluster create -f tkc.conf --tkr v1.23.5---vmware.1-tkg.1-zshippable -v 9
compatibility file (/Users/cpamuluri/.config/tanzu/tkg/compatibility/tkg-compatibility.yaml) already exists, skipping download
BOM files inside /Users/cpamuluri/.config/tanzu/tkg/bom already exists, skipping download
writing checksum "35b821d4f711879038d181eafe825a7cbf166e87e43f1f743c817b1f4e531ff1" to file "/Users/cpamuluri/.config/tanzu/tkg/providers/providers.sha256sum"
Using namespace from config: a-ns-test
You are trying to create a cluster with kubernetes version 'v1.23.5+vmware.1-tkg.1-zshippable' on vSphere with Tanzu, Please make sure virtual machine image for the same is available in the cluster content library.
Do you want to continue? [y/N]: y
Validating configuration...
Error: failed to create Tanzu Kubernetes Cluster service for vSphere workload cluster: Overlaying (in following order: overlay.yaml, 01_plans/prod.yaml, 03_customizations/annotate_os_info.yaml, 03_customizations/registry_skip_tls_verify.yaml): Document on line 03_customizations/registry_skip_tls_verify.yaml:7: Expected number of matched nodes to be 1, but was 0
Error: exit status 1