Release Name Migration - Vault

Summary

Migrate Vault to an explicit HelmRelease spec.releaseName as part of the phased package migration tracked by the release-name migration epic.

Background

Issue #680 identified duplicate/redundant naming patterns caused by default Helm release naming behavior. A prior all-at-once attempt was closed and documented that migration must be incremental per package due to hardcoded references.

Phase 1 framework created here:

• optional package-level releaseName support in schema
• conditional rendering support in HelmRelease helper
• tests validating default and override behavior

Scope

• Set addons.vault.releaseName default to the intended stable value: vault.
• Ensure Vault manifests render and reconcile with the new release name.
• Identify and update any hardcoded name references impacted by Vault release name changes in:
  • Big Bang chart templates/values
  • package-level defaults/overrides
  • tests in this repo
  • Vault package repo (if applicable)
• Add/adjust unit tests and integration checks specific to Vault.
• Add upgrade note documenting behavior and expected impact.

Out of Scope

• Migrating other packages in this issue.
• Broad refactors unrelated to Vault release naming.

Implementation Notes

• Use stable, non-versioned naming.
• Keep migration blast radius limited to Vault.
• If any cross-package reference is found, open a follow-on issue and link it.

Validation Plan

• Helm unittest coverage for Vault HelmRelease releaseName behavior.
• Chart lint and template render checks.
• CI package test lane including Vault labels.
• Upgrade validation from the most recent previously supported BB release to current BB release to ensure no regressions emerged.