Backport of Bug fix: Update KV data when you change the version of a nested secret into release/1.15.x

[hc-github-team-secure-vault-core]

Backport

This PR is auto-generated from #25152 to be assessed for backporting due to the inclusion of the label backport/1.15.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:
@Monkeychip
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: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

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

---

Fixes #25029.

Regression caused by #24224

This was caused because we were using a tracked property (this.codeMirrorSring) for the secret data and we needed a getter that relied on the this.args.secret model arg. The secret model was updating and thus the secretData was correct behind the scenes but the tracked property was not re-firing because it didn't rely on anything that was triggering a re-fire of the property.

• Enterprise tests pass. I realize this isn't an enterprise area, but being conservative on all things KV.
• Make sure new test coverage fails without the changes (suggestion by Claire, thank you).

---

Overview of commits

• a4c8ce6

[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

---

temp 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.}

[github-actions]

CI Results:
All Go tests succeeded! ✅