CustomResourceGate reconcilers should filter by owned CRDs #910
Description
What happened?
Providers are getting a lot of unnecessary debug log messages from the CustomResourceGate reconciler which is reconciling ALL CRDs instead of just the CRDs that the provider owns and is responsible for.
This is wasting CPU, memory and cluttering logs with useless messages.
How can we reproduce it?
Look at the debug logs for the latest provider-helm when provider-family-aws providers are also installed:
2026-01-28T02:53:06.074Z DEBUG provider-helm gvk is ready {"gvk": "autoscaling.aws.upbound.io/v1beta1, Kind=AutoscalingGroup"}
2026-01-28T02:53:06.074Z DEBUG provider-helm gvk is ready {"gvk": "autoscaling.aws.upbound.io/v1beta2, Kind=AutoscalingGroup"}
2026-01-28T02:53:06.074Z DEBUG provider-helm gvk is ready {"gvk": "autoscaling.aws.upbound.io/v1beta3, Kind=AutoscalingGroup"}
2026-01-28T02:53:06.075Z DEBUG provider-helm gvk is ready {"gvk": "autoscaling.aws.upbound.io/v1beta1, Kind=Notification"}
2026-01-28T02:53:06.076Z DEBUG provider-helm gvk is ready {"gvk": "ec2.aws.upbound.io/v1beta1, Kind=TransitGatewayMulticastDomainAssociation"}
2026-01-28T02:53:06.076Z DEBUG provider-helm gvk is ready {"gvk": "docdb.aws.upbound.io/v1beta1, Kind=ClusterSnapshot"}
2026-01-28T02:53:06.077Z DEBUG provider-helm gvk is ready {"gvk": "ec2.aws.upbound.io/v1beta1, Kind=VPCPeeringConnectionOptions"}
2026-01-28T02:53:06.077Z DEBUG provider-helm gvk is ready {"gvk": "ec2.aws.upbound.io/v1beta2, Kind=VPCPeeringConnectionOptions"}
2026-01-28T02:53:06.078Z DEBUG provider-helm gvk is ready {"gvk": "kubernetes.crossplane.io/v1alpha1, Kind=ObservedObjectCollection"}
2026-01-28T02:53:06.078Z DEBUG provider-helm gvk is ready {"gvk": "iam.aws.upbound.io/v1beta1, Kind=SAMLProvider"}
2026-01-28T02:53:06.078Z DEBUG provider-helm gvk is ready {"gvk": "cloudwatchevents.aws.upbound.io/v1beta1, Kind=BusPolicy"}
2026-01-28T02:53:06.079Z DEBUG provider-helm gvk is ready {"gvk": "s3.aws.upbound.io/v1beta1, Kind=BucketCorsConfiguration"}
2026-01-28T02:53:06.080Z DEBUG provider-helm gvk is ready {"gvk": "lambda.aws.upbound.io/v1beta1, Kind=FunctionEventInvokeConfig"}
2026-01-28T02:53:06.080Z DEBUG provider-helm gvk is ready {"gvk": "lambda.aws.upbound.io/v1beta2, Kind=FunctionEventInvokeConfig"}
What environment did it happen in?
Crossplane version: 2.1.3