Why is the targetSelectors on EnvoyExtensionPolicy or BackendTrafficPolicy namespace bound? #7344
Description
We use the mergedGateways feature and will have a lot of Gateway resources spread out across different namespaces to generate a central Gateway in the namespace where the Envoy Gateway controller runs.
However, on each of these gateways, we'd like to configure a BackendTrafficPolicy and EnvoyExtensionPolicy. To avoid duplication of these resources to each namespace, We'd like to use the targetSelectors parameter to target Gateway resources accross all namespaces. However, it seems this selector only works within a namespace boundary. With mergedGateways, we would expect that to work, but it doesn't. Is this working a designed or a bug? If it is working as designed, can it be considered to change?