...

The tool should ensure that the features set are valid. This is done by marking features as dependent on others internally.

For this change specifically, all features rely on at least MV 3.3-IV0 (since this enables the writing of features to the metadata topic as per KIP-584). Any command to try to set a feature (either via storage or upgrade tool) when metadata version is below 3.3-IV0 will fail. (If an RPC is sent, it will also fail as the version is not supported)

Transaction version does not rely on any other components, so as long as metadata is 3.3-IV0, there are no failures. 

Test Plan

Tests will be added to the StorageToolTest and FeatureCommandTest.

...