[backport v2.13] ShardID is not taken into account for Watches statements

[rancherbot]

This is a backport issue for #4275, automatically created via GitHub Actions workflow initiated by @0xavi0

Original issue body:

This was reported in #4183 and confirmed.

The Bundle reconciler is filtering its requests using:

WithEventFilter(sharding.FilterByShardID(r.ShardID))

However, a Watches function is also being used, which monitors changes in Clusters and retrieves the Bundles that are deployed in those Clusters.
In that case, the request is being enqueued without filtering by ShardID, which can lead to a controller without an assigned ShardID processing that request.

More controllers might be affected by this.

[adibrastegarnia]

I use this issue for further discussion of this topic. I am not sure this PR #4282 solves the issue completely. Let's assume I labeled my GitRepo and bundle to be shard-0 and cluster which is independent of these objects labeled in shard-1. If you create a gitRepo first and then add a cluster later, the cluster changes trigger bundle controller but since cluster is in shard-1 it cannot find any bundles because they are in shard-0. Am I missing something here? cc @kkaempf @0xavi0

[0xavi0]

@adibrastegarnia Would you mind creating a different issue for the case that concerns you so we can keep track of it?
I was about to close this one because the subject of the issue was already covered by the PR that was already merged.

Thanks!