This:

• Adds tracking in SQL Server for when we're inside an aggregate method (Count, Max...). The flag was introduced on SqlServerQueryCompilationContext.
  • This maybe isn't the ideal place, because the flag is only temporary translation state, and does not apply to all of compilation.
  • But it's currently the only place shared across SqlServerQueryableMethodTranslatingExpressionVisitor and SqlServerSqlTranslatingExpressionVisitor. We can think about a better way to preserve state data across the different visitors during the translation process.
• Then, if the flag is on and we see the new OPENJSON-based subquery translation for Contains, we convert it to the old IN+constants translations, as if the SQL Server compatibility level were too low.

One note: we could instead refrain from producing the OPENJSON translation altogether (return null from TranslatePrimitiveCollection), and let the general relational fallback produce the old IN+constants translation. But this would block simplifications that pattern-match on top of the OPENJSON translation (currently we only have TranslateElementOrDefault which does that for SQL Server).

Fixes #32374