UI: add copyable paths for CLI and API commands to kv v2

[hellobontempo]

This adds a paths tab to the kv engine secret view that gives users the API and CLI paths for copying, plus sample commands

example:

[github-actions]

Build Results:
All builds succeeded! ✅

[github-actions]

CI Results:
All Go tests succeeded! ✅

[kiannaquach]

[Future improvement + for different project]: Refactor the DocLink to use the HDS Inline Link. Stylistically it doesn't make a big difference, but might be good to have.

[hellobontempo]

Thanks for the note! I'm trying to decide the best way to adopt the HDS links 🤔 They're great out of the box in place of <LinkTo>.

But for our other link components I'm going back and forth a lot. We could get rid of our components all together and just use HDS components directly...however I like that <DocLink> prefills the path. It was really useful having the host default for when the website changed hosts, we only had to update links in a few places instead of everywhere that had the old web address.

One thought is to have an @inline arg that renders the HDS inline component. Another option is to that if the component has an @icon arg it renders a standalone link, otherwise it renders inline.

[kiannaquach]

Ahh yeah, links are a tough one to make decisions about! I like the idea of using HDS components out of the box since it eliminates confusion on what component to use. We don't have a component library with documentation so it's hard to figure out what components to use whereas hds is more explicit when comes to that. However, I also love that the DocLink makes it convenient so we don't have to prefix doc links.

[hellobontempo]

Yeah - I think this is a great point that figuring out a component library could be useful to consider after HDS adoption is complete if we still have a bunch of components floating around. We previously used storybook but it became too difficult to maintain

[hashishaw]

✨ nice work!