Currently the test relies on the test command testCommandFeatureFlaggedOnLatestFCV that we created to be only defined on the latest FCV and not on last-lts FCV. So for example if we committed the code to define that command in FCV X.Y, then once X.Y becomes last-lts this test will break.

We saw this in SERVER-110184 when the original commit on 8.2 from SERVER-100448 was backported to 8.0, which then caused the test on master to start failing.

We should investigate if we can make testing the interaction command registration on startup with FCV more resilient to releases.

At the very least the simplest thing to do is to keep editing the name of the command before a new release becomes last-lts and keep making new TODO tickets to change it again for the next last-lts release so as part of the quick fix for SERVER-110184 we will need to edit the name once 9.0 becomes last-lts,- or potentially once 8.2 becomes last-lts if SERVER-110184 needs to be backported to 8.2.- (SERVER-110184 will be backported to 8.2 but the command has a different name). We should also remove references to the old testCommandFeatureFlaggedOnLatestFCV command in all_commands tests once 8.3/8.2 are last-lts

I think this ticket only needs to be done before 9.0 becomes last-lts