Incorporate a built-in list of well-known CRDs

[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

There are practical issues with CRD discovery in complex programs that often leads to the error message:

failed to determine if the following GVK is namespaced: ...

See #3176 for example. The original motivation for making the "namespaced" determination is documented in #2904.

While we do make efforts to cache the CRDs (see #3299), some corner cases may still remain. This ticket is about introducing a built-in list of well-known CRDs, specifically the scope information with which to pre-populate the cache. Imagine we were to generate a data file based on extracting CRDs from a catalog of known Helm charts and Operators. The combination of a well-known set plus the dynamic caching will probably eliminate this issue for most users.

Affected area/feature