Is your feature request related to a problem? Please describe.

I have to deploy the same zarf package more than once to the same cluster, using a different namespace each time. The number of deployments needed and namespace names are both not always known in advance.

Describe the solution you'd like

• Given I have a Zarf variable called NAMESPACE and a zarf.yaml component like:

components:
  - name: my-app
    required: true
    charts:
    - name: my-app
      localPath: ./
      namespace: "###ZARF_VAR_NAMESPACE###"
      version: 1.2.3
      valuesFiles:
      - values.yaml

• When zarf package deploy --set NAMESPACE=foo is run and followed by zarf package deploy --set NAMESPACE=bar
• Then "my-app" is deployed to the namespace "foo", followed by a 2nd instance of "my-app" being deployed to the namespace "bar".

Describe alternatives you've considered

• Using create-time variables, but that would require managing multiple built .tar.zst files which is undesirable
• Using multiple optional components, but that's (a) an ugly hack, and (b) requires both the namespace names as well as the maximum possible number of deployments to be known in advance.