fix(idempotency): make kafka-storage commands return correct changed_when status

[sverrehu]

Description

Before this PR, in KRaft mode, commands running kafka-storage had no explicit changed_when, so they would always report that they changed the system.

This PR sets changed_when: false for kafka-storage info and kafka-storage random-uuid, none of which changes anything on the hosts. It also sets changed_when for the kafka-storage format command, based on the output from the command.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Tested in our local provisioning pipeline.

Checklist:

• Any variable/code changes have been validated to be backwards compatible (doesn't break upgrade)
• I have added tests that prove my fix is effective or that my feature works
• If required, I have ensured the changes can be discovered by cp-ansible discovery codebase
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[sverrehu]

*knock, knock*

[sverrehu]

It is still like this for 8.0.0, with an even increasing number of falsely reported changes recently. cp-ansible devs used to listen to their users previously, but it appears that you now just ignore contributions from outsiders. If that is the new policy, please let us know. Thank you!

@mansi-jain-1206 @rrbadiani @varsharma-12 (I just picked three recent mergers.)

Cc: @erikgb @oc