What happened:
I had an issue with the fleet auto scaler trying to scale to -41 replicas.
As I see, fleet auto scaler with Counter policy does not respect the game server's namespace when calculating the current game server count.
I have different namespaces like qa1, qa2, etc., and each has a fleet my-fleet, where 1-2 game servers are launched.
I did debug and saw that ListGameServersByFleetOwner returned all game servers in a cluster with fleet owner name my-fleet.
I'm expecting that fleet and game servers are namespaced resources.
I did the simple fix - we just added namespace name to fleet name, like my-fleet-qa1, my-fleet-qa2

What you expected to happen:
Fleet is the namespaced resource. I need to be able to create a fleet with the same name in different namespaces with CountsAndLists policy.

How to reproduce it (as minimally and precisely as possible):

1. Create 2 fleets with the same name in different namespaces.
2. Create 2 fleet autoscaler with Counter policy
3. Just autoscale them.

Anything else we need to know?:

Environment:

• Agones version: 1.42
• Kubernetes version (use kubectl version): 1.29
• Cloud provider or hardware configuration: GKE
• Install method (yaml/helm): helm
• Troubleshooting guide log(s):
• Others: