KAFKA-15367: Test non-JBOD to JBOD transition

[lh0156]

Corresponding JIRA ticket: https://issues.apache.org/jira/browse/KAFKA-15367

What is the purpose of this change?

Add an integration regression test for a broker transitioning from non-JBOD metadata to JBOD-supported metadata. Before IBP_3_7_IV2, the controller's broker registration must not contain log directories. After upgrading to IBP_3_7_IV2, the broker must re-register and publish the directory ID that it actually loaded.

This verifies the externally observable behavior handled by BrokerRegistrationTracker, rather than only asserting that the metadata-version update request succeeded.

Brief change log

• Start a one-broker, one-controller KRaft cluster with IBP_3_7_IV1.
• Assert that the broker registration initially has no directories.
• Upgrade metadata.version to IBP_3_7_IV2.
• Assert that the broker re-registers with the loaded directory UUID.

Testing

• TDD: added the state-transition assertions first; the test fixture's formatting behavior was then accounted for by deriving the expected UUID from the broker's loaded LogManager state.
• ./gradlew :server:test --tests org.apache.kafka.server.KRaftClusterTest.testNonJbodToJbodTransition --no-build-cache --console=plain
• ./gradlew :server:test --tests org.apache.kafka.server.KRaftClusterTest --no-build-cache --console=plain
• ./gradlew spotlessCheck --no-build-cache --console=plain
• git diff --check

[github-actions]

A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the triage label
should be removed to prevent this automation from happening again.