JSON projections fail on Azure SQL

[AndriySvyryd]

Several tests, like AdHocJsonQuerySqlServerJsonTypeTest.Contains_on_nested_collection_with_init_only_navigation and ComplexJsonCollectionSqlServerTest.Count are failing with

JSON data type cannot be used in OpenJson function.

SELECT [r].[Id], [r].[Name], [r].[OptionalRelated], [r].[RelatedCollection], [r].[RequiredRelated]
FROM [RootEntity] AS [r]
WHERE (
    SELECT COUNT(*)
    FROM OPENJSON([r].[RelatedCollection], '$') AS [r0]) = 2

[roji]

JSON data type cannot be used in OpenJson function

This error means that the JSON data type is still being in use with Azure SQL; #36596 disabled that, but it seems like we still don't flow forward commits from release/10.0-rc1 to release/10.0 and to main (I remember us mentioning that this isn't in place recently). I verified that when running e.g. ComplexJsonCollectionSqlServerTest.Count on release/10.0-rc1 (as opposed to release/10.0), the test passes (the JSON data type doesn't get used).

Do we know how to set up the flow or who to contact? Or should I manually cherry-pick this commit to the forward branches?

[roji]

One additional note: #36596 did leave out updating [SqlServerCondition(SqlServerCondition.SupportsJsonType)] to not run JSON type tests on Azure SQL, so tests in AdHocJsonQuerySqlServerJsonTypeTest (and possibly other test suites) do fail when running rc.1 against Azure SQL. After correcting this all query tests pass against SQL Azure (apart from various flakiness/availability failures).

I'll fix this in release/10.0, but as this is a temporary test-only issue (and we don't run CI against Azure SQL), it shouldn't be important (probably not worth patching release/10.0-rc1).