HOTFIX: fix failed cases in FeatureCommandTest

[FrankYang0529]

CI sample: https://github.com/apache/kafka/actions/runs/11051663030/job/30710832201?pr=17165

FAILED ❌ FeatureCommandTest > testDescribeWithKRaftAndBootstrapControllers [1] Type=Raft-Isolated, MetadataVersion=3.7-IV0,Security=PLAINTEXT
FAILED ❌ FeatureCommandTest > testDowngradeMetadataVersionWithKRaft [1] Type=Raft-Isolated, MetadataVersion=3.3-IV1,Security=PLAINTEXT
FAILED ❌ FeatureCommandTest > testDescribeWithKRaft [1] Type=Raft-Isolated, MetadataVersion=3.3-IV1,Security=PLAINTEXT

Committer Checklist (excluded from commit message)

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

[chia7712]

The failed test is caused by #17112, which added IBP_4_0_IV3, and the failure is due to the tool-module cache.

@mumrah This is the issue we discussed over the email thread. Perhaps we should always run certain modules to ensure the PR is covered by sufficient integration tests?

[mumrah]

Looks like the tests were failing on the PR, so this should not have been merged.

https://github.com/apache/kafka/actions/runs/11027485627

[mumrah]

@chia7712 I agree we should eventually have some "acceptance" tests which do some high level sanity checks. In this case, a change to MetadataVersion (located in server-common) will cause pretty much all tests to run except maybe client.

[chia7712]

Looks like the tests were failing on the PR, so this should not have been merged.

you are right. I was checking the wrong CI :(

[mumrah]

Thanks for the fix @FrankYang0529!

[mumrah]

I verified that the test is passing locally. Merging now to un-break trunk

[kamalcph]

Thanks @FrankYang0529 for fixing this test!