PeerId inconsistent between subkey and the printout when starting the node

[kaichaosun]

The subcommand (generate-node-key) of subkey prints a PeerId.
Starting the node with --node-key specifying the generated private key printout another PeerId.

[romanb]

This is caused by a bug / regression in generate-node-key, which at some point started to hex-encode the key it writes to the file. When the node is started with --node-key-file there is no hex-decoding taking place, so in effect the node gets a different secret key and thus a different keypair and peer ID than what was seen by generate-node-key. See #7052 (comment).

[tomaka]

Closing as duplicate of #7045