Release resource should integrate with the CRD cache

[EronWright]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

The provider maintains a cache of CRDs across resources, to enable various resources to determine whether a given kind is namespaced. For example, the ConfigFile resource creates a child resource for each object in the manifest file, and assigns a resource base derived from the object's name. If the kind is namespaced, the context namespace (e.g. default) must be included in the name, in order to arrive at a canonical name. This, in turn, affects other features like the supported config.kubernetes.io/depends-onn annotation (ref). See #2904 for more information.

At present, the Release resource doesn't contribute to the CRD cache, because it doesn't create child resources (e.g. of type kubernetes.apiextensions.k8s.io/v1.CustomResourceDefinition).

As I outlined in #3186 (review), the Release resource should populate the CRD cache.

Affected area/feature