Is your feature request related to a problem? Please describe.
Currently the remoteNamespace must be set on the store. But let's imagine you have a store equipped with credentials to talk to the whole remote cluster (kubernetes provider) we have to define a SecretStore for each remote Namespace.

Describe the solution you'd like
Why not just let the PushSecret set the Namespace where the secret should end up? This can also be an optional overwrite to not break the current flow.

Describe alternatives you've considered
Open for other suggestions.