As documented in this test, any attempt to add a view to a database should fail if there are views in the database that are unsupported by the current FCV. This scenario would usually occur if a user creates views using new features under a higher FCV and then downgrades the FCV after.

Downgrading the FCV does not affect view catalogs, so all levels of view caching remain valid, and there is no opportunity for a view creation operation to observe that there is an existing view that is now incompatible. Only after the view catalog somehow gets reloaded do we get the desired behavior.

We should either add stricter checking and re-enable this test or document somewhere that it's acceptable for there to be lag between an FCV downgrade and the enforcement of the no-new-view rule.