crypto: rename keys dir

[tac0turtle]

Description

• rename keys dir to keybase
• move keyring to own dir

Signed-off-by: Marko Baricevic marbar3778@yahoo.com

---

For contributor use:

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer

---

For admin use:

• Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
• Reviewers assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[codecov]

Codecov Report

Merging #5834 into master will not change coverage by %.
The diff coverage is 60.00%.

@@           Coverage Diff           @@
##           master    #5834   +/-   ##
=======================================
  Coverage   32.30%   32.30%           
=======================================
  Files         353      353           
  Lines       39461    39461           
=======================================
  Hits        12749    12749           
  Misses      25439    25439           
  Partials     1273     1273           

[tac0turtle]

@alessio to move keyring out of keybase i would need to move structs to be public. is this fine? I see that it was purposefully kept like this so not sure if we want it to change

[alessio]

to move keyring out of keybase i would need to move structs to be public.

Which structs @marbar3778 ?

[tac0turtle]

close in favor of #5866