New DDL FSMs (1 and 2) are failing in implicit multiversion variants because the sharded rename collection was not supported in v4.4.

There are 2 possible fixes:

• Allow exceptions with error code 13138 to be thrown (just v4.4 can throw such exception).
• Blacklist the FSMs from multiversion suites. In this case, it is not tested the compatibility of legacy path with v4.4 binaries, so it should not be the preferred options (verify if it makes sense to keep FSMs running in case of multiversion binaries).