Backport of [UI] - run colocated components codemod into release/1.20.x

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

Backport

This PR is auto-generated from #31397 to be assessed for backporting due to the inclusion of the label backport/1.20.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:
@zofskeez
This person should resolve the merge-conflict(s) by either:

• Manually completing the cherry picks into this branch
• Creating a new branch and manually cherry-picking all commits being backported

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.

---

Description

There were still a good number of component templates left in the templates/components directory. Ember has long supported (2019!) colocation of components and their templates. Handily, there is also a codemod that will do this change for you. There was one hiccup in that the codemod is old enough, it doesn't recognize some newer syntax, but there is also a PR to fix this issue.

This PR is the result of running this command in the ui directory:

npx github:apellerano-pw/ember-component-template-colocation-migrator#major-bump-ember-template-recast-v3-to-v6

JIRA ticket

TODO only if you're a HashiCorp employee

• Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
  • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
• ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
  of a public function, even if that change is in a CE file, double check that
  applying the patch for this PR to the ENT repo and running tests doesn't
  break any tests. Sometimes ENT only tests rely on public functions in CE
  files.
• Jira: If this change has an associated Jira, it's referenced either
  in the PR description, commit message, or branch name.
• RFC: If this change has an associated RFC, please link it in the description.
• ENT PR: If this change has an associated ENT PR, please link it in the
  description. Also, make sure the changelog is in this PR, not in your ENT PR.

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.
• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

---

Overview of commits

• 4a2b5bf

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
vault-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 1, 2025 4:06pm

[hashicorp-cla-app]

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

---

28 out of 29 committers have signed the CLA.

• kporter101
• steved
• timmjd
• kevin-loehfelm
• miagilepner
• zofskeez
• bosouza
• sgmiller
• akshya96
• Younique98
• tvo0813
• roooms
• VioletHynes
• ryancragun
• drivera258
• hellobontempo
• aslamovamir
• davidadeleon
• rculpepper
• Soromeister
• mickael-hc
• elliesterner
• himanshu-8693
• lursu
• wenzel-felix
• giogranda85
• zamoore
• meirish
• Pmoranga

---

Pmoranga seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already 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! ✅