ProviderConfigUsage creation blocked because providerconfig name > 63 characters

[SleepyBrett]

NOTE: I'm not sure where this issue belongs. So there is a duplicate on the primary crossplane repo just in case: crossplane/crossplane#3224

What happened?

Kubernetes object names (.metadata.name) supports a maximum length of 253 characters.

Kubernetes Label values (.metadata.labels[]) are limited to 63 characters in length.

Therefore if your ProviderConfig has a name that is > 63 charcters when you attempt to use it crossplane will block you with errors such as:

'connect failed: cannot track provider config usage: cannot apply ProviderConfigUsage:
      cannot create object: ProviderConfigUsage.helm.crossplane.io "5156973e-c7fc-4b6f-9697-8f0aea08d75f"
      is invalid: metadata.labels: Invalid value: "xx-xxxxxxxxxxxxxxxxxx-xxxxx-xxxxx-xxxxxx-xxxxxxxx-xx-xxxx-x-xxx-xx":
      must be no more than 63 characters'

How can we reproduce it?

Create a providerconfig with a name longer than 63 characters and then try and use it.

What environment did it happen in?

Crossplane version:
v1.6.3

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.