feat: add w3 name get-key command

[adamalton]

Fixes #1835.

[joshJarr]

LGTM, great shout.

[alanshaw]

This feels like half of the solution - how do I then use that key in a different w3 CLI?

Personally I'd call these:

w3 name export <keyId> > priv.key
w3 name import priv.key

[adamalton]

@alanshaw having both an import and an export command makes sense. Do you think that these should only be for doing one key at a time, or do you think that it would actually be a nicer user experience to be able to export all of your name keys at once into a single file, and then import them in bulk too? Or do you think that the common use case of w3 name functionality is typically only one or two names at a time?

[alanshaw]

IMO just one at a time...multiple would mean that there has to be a format to the exported file and I don't want to have to define that, or trust users to pick out a particular key from it. You also can't give it directly to something else that is able to read the keys (like programmatically to the library) without also making changes there.

[alanshaw]

...you could also add w3 name export --all later and augment w3 name import to be able to read one or many...

[github-actions]

package-lock.json changes

Click to toggle table visibility

Name	Status	Previous	Current
fs		-	0.0.1-security

[adamalton]

Now refactored as per Alan's suggestion, and tests added for additional fun and profit.

[github-actions]

Website preview 🔗✨

• 🙂 https://w3s.link/ipfs/bafybeigt7v325vfrqg4c5b7xvudi7huggkxph3desf5yf2fzafyjmfxfgq
• ⛅️ https://1e9f8e2c.web3-storage-staging.pages.dev

build log

[adamalton]

I think that the failing test here will be fixed by #2151.

[alanshaw]

Suggested change

"fs": "^0.0.1-security",