Fix namespace rendering in provisioner job

[trevorwhitney]

What this PR does / why we need it:

Fix rendering of namespace in provisioner job template when a secertNamespace is provided that's different from the release namespace.

Which issue(s) this PR fixes:
Fixes #8403

Special notes for your reviewer:

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• CHANGELOG.md updated
• Changes that require user attention or interaction to upgrade are documented in docs/sources/upgrading/_index.md

[MichelHollands]

LGTM

[basvdl]

Maybe we need the same fix for line 96... But only if we expect the user to set a templated var i.e.

  provisioner:
    additionalTenants:
      - name: foo-bar
        secretNamespace: "{{ .Release.Namespace }}"

Will result in:

          kubectl --namespace "{{ .Release.Namespace }}" create secret generic "enterprise-logs-provisioned-foo-bar" \
            --from-literal=token-write="$(cat /bootstrap/token-write-foo-bar)" \
            --from-literal=token-read="$(cat /bootstrap/token-read-foo-bar)"

[trevorwhitney]

yeah, I would be surprised if a user wanted to set this to a templated value. let's wait for a specific request for that functionality before adding it.