Backport of NET-581 - Added vault namespace in helm into release/1.1.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #2841 to be assessed for backporting due to the inclusion of the label backport/1.1.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@absolutelightning
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: unable to process merge commit: "c7342840f1e1f0ca6ec613332ae3dfdd12be19cc", automatic backport requires rebase workflow

The below text is copied from the body of the original PR.

---

Changes proposed in this PR:

• Adds vaultNamespace in secretsBackend.vault in values.yaml
• This namespace is used for Vault namespace, this introduces one more way to specify namespace other than
  "{"connect": [{ "ca_config": [{ "namespace": "value"}]}]}" in connectCA.additionalConfig
• If vaultNamespace is present, it automatically adds annotation below to the templates.

    vault:
      agentAnnotations: |
        vault.hashicorp.com/namespace: vaultNamespace

How I've tested this PR:
a. CI
b. Updated test TestVault_VaultNamespace
Test Steps -

1. kind create cluster --name=dc1
2. kind create cluster --name=dc2
3. cd acceptance/test/vault
4. go test ./... -p 1 -timeout 2h -failfast -no-cleanup-on-failure -debug-directory=/tmp/debug -use-kind -enable-multi-cluster -kube-contexts=kind-dc1,kind-dc2  -run ^TestVault

Output -

asheshvidyut@absolutelightning-H2GX766V9T acceptance/tests (NET-581-Configure-Vault-namespaces-for-Connect-CA-via-Helm-Stanza) » go test ./... -p 1 -timeout 2h -failfast -no-cleanup-on-failure -debug-directory=/tmp/debug -use-kind -enable-multi-cluster -kube-contexts=kind-dc1,kind-dc2  -run ^TestVault
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/api-gateway	0.492s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/basic	0.547s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/cli	0.529s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/cloud	0.565s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/config-entries	0.524s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/connect	0.556s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/consul-dns	0.543s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/example	0.540s
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/ingress-gateway	0.553s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/metrics	0.555s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/partitions	0.561s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/peering	0.568s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/sameness	0.552s
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/snapshot-agent	0.572s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/sync	0.554s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/terminating-gateway	0.553s [no tests to run]
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/vault	916.339s
ok  	github.com/hashicorp/consul-k8s/acceptance/tests/wan-federation	0.587s [no tests to run]

How I expect reviewers to test this PR:

Checklist:

• Tests added
• CHANGELOG entry added

---

Overview of commits

• bc79b0a - 3ee878c - 10ec942 - 9935a1b - 4097b48 - 3f8c4f3 - 5339dd9 - c734284 - 9e2f11d - 9d2ba12 - 8cc2117 - 01f3e95 - 6917abb - ad710bf - fdd7cf1 - d3e0323 - 7b3482b - 532210d - fd469b6 - 7c870ea - cac8d3a - c4a0f8a - 6c692df - d05f340 - 261f379 - 3d9c05c - 228b423 - ef1710d - 0827f81 - 306632b - faec4c2 - b1fd0fd - 636208f - 666331a - ffe4b1f - c8478a0 - ecfff91 - 959431f - 8f52b7c - 1f3e23a - ed1026e - 825fb42 - b840d32 - ed2573a - a47a3d8 - 8a7b8bd - 3c4291c - 4523282 - af7e617 - 124cc4d - 4be3cea - 7c13074 - d6da52e - 5f6a200

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

15 out of 16 committers have signed the CLA.

• hc-github-team-consul-core
• zalimeni
• thisisnotashwin
• missylbytes
• nathancoleman
• curtbushko
• t-eckert
• sarahalsmiller
• hashi-derek
• jm96441n
• wilkermichael
• DanStough
• absolutelightning
• trevorLeonHC
• david-yu
• Paul Glass

---

Paul Glass seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}