`ClusterProviderConfigUsage` appears as a managed resource

[tvandinther]

What happened?

clusterproviderconfigusages.http.m.crossplane.io is listed as a ManagedResourceDefinition. This does not follow the expected design pattern as compared with the upjet generated providers.

For example, the provider-azuread offers 2 providerconfigusages resources. One cluster and one namespace scoped. There are also 2 which are generated by this provider, presumably by the provider runtime.

I encountered errors in the provider due to a missing ClusterProviderConfigUsage CRD. This was fixed when adding it to my ManagedResourceActivationPolicy but that didn't seem right hence raising this issue. My understanding is that wherever ClusterProviderConfigUsage is used in this provider's code, it should be just a ProviderConfigUsage, specifically providerconfigusages.http.crossplane.io or providerconfigusages.http.m.crossplane.io.

How can we reproduce it?

Install v1.0.13 of this provider and list all mrds.

What environment did it happen in?

Crossplane version:

v2.0.2

[johnnycube]

I can verify this behaviour and would argue that all definitions should be MRDs