Better UX for consensus key change

[brentstone]

The consensus key change UX should be improved, as many validators did not properly complete the process and ended up jailed. Furthermore, some logging seems to be confusing to some users.

Would like to address, at a minimum, the Issues with this process that were originally brought up in #2643 and #2645.

After successful submission of a consensus key change tx, the CLI output should warn / guide the validators on what actions they must take next: generating a new priv key json for CometBFT, switching to its use after pipeline length epochs (2 epochs), restarting their node with the new keys in a timely manner, consequences if not done properly (downtime jailing).

[cwgoes]

@brentstone estimate: hours/days