Keyring migration doesn't migrate key names correctly

[amaury1093]

Summary of Bug

After keyring migration, we can't keys show by name anymore

Version

6e70d25, though it's probably after #9695

Steps to Reproduce

• ./build/simd is a master node built with above commit hash
• ./build/v042_node is a v0.42.9 node

Add a key on v042

➜  cosmos-sdk git:(master) ./build/v042_node keys add jack --keyring-backend test

- name: jack
  type: local
  address: cosmos15zz5edm79ga3jr6qd2sq5jsthcgutde5emtnhh
  pubkey: cosmospub1addwnpepq2j7xj9esq378vx8yjgrc3k93kkdaetlsn94kjkyj6xzmkf8aggaxpz4as2
# snip

Make sure the key shows up

➜  cosmos-sdk git:(master) ./build/v042_node keys show jack --keyring-backend test
- name: jack
  type: local
  address: cosmos15zz5edm79ga3jr6qd2sq5jsthcgutde5emtnhh
  pubkey: cosmospub1addwnpepq2j7xj9esq378vx8yjgrc3k93kkdaetlsn94kjkyj6xzmkf8aggaxpz4as2
# snip

Run the same command with the master keyring

➜  cosmos-sdk git:(master) ./build/simd keys show jack --keyring-backend test
Error: jack is not a valid name or address: decoding bech32 failed: invalid bech32 string length 4
Usage:
  simd keys show [name_or_address [name_or_address...]] [flags]

Notes:

1. ./build/simd keys show jack.info --keyring-backend test works and shows the correct key. I think we might have forgotten to migrate the name itself
2. ./build/simd keys list --keyring-backend test also works and shows jack's key.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned