KAFKA-17171: Add test cases for STATIC_BROKER_CONFIGin kraft mode

[frankvicky]

JIRA: KAFKA-17171

The patch should include following test cases.

1. a topic-related static config is added to quorum controller. The configs from topic creation should include it, but describeConfigs does not.
2. a topic-related static config is added to quorum controller. The configs from topic creation should include it, and describeConfigs does if admin is using controller.bootstrap
3. a topic-related static config is added to broker. The configs from topic creation should NOT include it, but describeConfigs does.
4. a topic-related static config is added to broker. The configs from topic creation should NOT include it, and describeConfigs does not also if admin is using controller.bootstrap
   for another, the docs of STATIC_BROKER_CONFIG should remind the impact of "controller.properties"
   BTW, those test cases should leverage new test infra, since new test infra allow us to define configs to broker/controller individually.

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[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.

[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.

[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.

[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.

[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.

[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.

[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.

[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.