Allow ability to override a components namespace when imported into a bundle.

[zachariahmiller]

Is your feature request related to a problem? Please describe

I would like to be able to override the namespace a chart in a zarf package is deploying into when i create a bundle. Currently in zarf, namespace is a mandatory field and depending on the use case that makes it difficult to reuse packages. For example

This package is used for dev dependencies in the SWF individual packages. For SWF integration, i cannot use this package as it stands today because it just deploys over/overwrites itself in the dev-postgres namespace.

Describe the solution you'd like

something like:

kind: UDSBundle
metadata:
  name: uds-stuff
  version: dev

packages:
  - name: dev-postgres
    repository: ghcr.io/defenseunicorns/packages/uds/dev-postgres
    ref: 0.0.1
  - name: dev-postgres-sonarqube
    repository: ghcr.io/defenseunicorns/packages/uds/dev-postgres
    ref: 0.0.1
    overrides:
      postgres:
        postgresql:
          namespace: dev-postgres-sonarqube

I dont feel strongly about the syntax at all except for a general desire for it to be as simple and clear as possible.

Describe alternatives you've considered

For the example case i've entertained using the zalando operator instead of the existing chart. Also creating multiple duplicae optional components in the source zarf package that override the namespace

Additional context

I can see multiple places where this might break down/would still very much depend on how the upstream package was composed. For example, in the common dev postgres chart, the zarf package does a wait on the cluster resource that also depends on knowing the namespace

[zachariahmiller]

Just a note a more reasonable (not dev dependency) example of this issue is reuse of the gitlab runner package https://github.com/defenseunicorns/uds-package-gitlab-runner

[UncleGedd]

Relates to #372