UI: Add copy button for secret path

[hellobontempo]

Description

Adds a copy button for secret paths in both kv v2 and v1 secrets engines

TODO only if you're a HashiCorp employee

• Backport Labels: If this PR is in the ENT repo and needs to be backported, backport
  to N, N-1, and N-2, using the backport/ent/x.x.x+ent labels. If this PR is in the CE repo, you should only backport to N, using the backport/x.x.x label, not the enterprise labels.
  • 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.

[github-actions]

CI Results:
All Go tests succeeded! ✅

[github-actions]

Build Results:
All builds succeeded! ✅

[hellobontempo]

✅ enterprise tests

[Monkeychip]

My concern here would be, if in the future, someone uses this component with both a secretPath and a pageTitle the behavior would be unexpected. It seems to me that the design of this is that they are mutually exclusive: you can't have both, but only one. I checked the code and that seems to be the case.

Some thoughts:

1. Create a kv-page-header.js file to have an assertion that you can't have both assigned.
2. You could just stick with one property but then this else if block doesn't work.
3. ... 🤔 maybe it's not a concern.

[Monkeychip]

I think I like option 1 because it also allows us to add documentation. But you've already gone above and beyond for a simple request so I'll make this comment non-blocking.

[hellobontempo]

Thanks for asking about this!

This is just for the aria-label and so it follows the same logic flow for the header above, since they're mutually exclusive and you can only have one header text 😅 . I think the conditional above makes that pretty clear 🤔 I feel like a component and documentation would be overly verbose for such a simple component

[Monkeychip]

Great cleanup and test coverage. A non-blocking comment.