Devtools/yes_wallet: always output the consensus_key_mapping

After offline discussions, it seems that overriding the the delegates pkh by the consensus keys directly into the public_key_hashs could be a bit misleading in some case. To avoid that, we restore the usual behavior but we output a new consensus_keys_mapping file, by default, that maps delegates to their respective consensus keys. Thus, if needed, one simply need to open this file and retrieve the consensus key.

Manually testing the MR

Simply run dune exec devtools/yes_wallet/yes_wallet.exe -- create from context ./some_data_dir in ./tmp-yes-wallet --network mainnet --active-bakers-only and look for the consensus_keys_mapping located in ./tmp-yes-wallet

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR