UI: Remove custom tag class and replace with Hds::Badge

[lane-wetmore]

Description

Replaces instances of the tag class in favor of Hds::Badge and removes associated styles. For most of these, the badge is identical. A few may now have improved spacing.

This also establishes a pattern for code elements within a larger surrounding text. In these cases, we will use Hds::Text:Code with class code-in-text to have a uniform element appearance.
Example:

Before:

After:

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.

[hashicorp-cla-app]

All committers have signed the CLA.

[github-actions]

Build Results:
All builds succeeded! ✅

[github-actions]

CI Results:
All Go tests succeeded! ✅

[hellobontempo]

Great work on your first PR! 🎉 Excellent attention to detail. There are just a few cleanup items to address. I didn't comment on all of them, but we'll also want to remove any has-text-<color> classes from the added badges.

It might be nice to update the title to mention that we're replacing it with the hds component and removing the tag class all together. Something like UI: Remove custom tag class and replace with Hds::Badge.

There are also some tests failing, so we need to address those. Let me know if you want to pair through running tests locally!

[hellobontempo]

These should all be code elements like the one below.

[lane-wetmore]

What do you think about adding a heavier weight to these code elements to maintain their contrast to the rest of the content?

Code w/ weight:

Code w/o weight:

Previous tag class:

[hellobontempo]

This is another one that doesn't need concat if you prefer to write it this way:

Suggested change

	<Hds::Badge @text={{concat "version " (or @model.version "1")}} data-test-kv-version-badge />
	<Hds::Badge @text="version {{or @model.version '1'}}" data-test-kv-version-badge />

[hellobontempo]

Well done! Great work on your first PR 🎉 excellent description and inclusion of screenshots! ✨ Before merging, we want to make sure enterprise tests pass so we don't accidentally break enterprise when this is merged there

[hellobontempo]

I went ahead and added the backport/1.18.x label, if the cherry-pick is successful after merge then a backport PR will open. I think it's worthwhile backporting it to maintain branch parity since this work spans quite a few files and is low risk to backport.