EES-5256 Opt-out of OPENJSON subquery transformation in time periods query and revert #5002

[benoutram]

This PR opts-out of the OPENJSON subquery transformation of the location id's in the time periods metadata query and revert back to using an SQL IN clause as was the behaviour prior to updating to Entity Framework Core 8.

Prior to this change the query is translated using an OPENJSON subquery

SELECT DISTINCT [o].[Year], [o].[TimeIdentifier]
 FROM [Observation] AS [o]
WHERE [o].[SubjectId] = @__8__locals1_query_SubjectId_0
AND [o].[LocationId] IN (
    SELECT [l].[value]
    FROM OPENJSON(@__locationIds_1) WITH ([value] uniqueidentifier '$') AS [l]
)

With this change, for multiple location id's the query is translated using IN

SELECT DISTINCT [o].[Year], [o].[TimeIdentifier]
FROM [Observation] AS [o]
WHERE [o].[SubjectId] = @__8__locals1_query_SubjectId_0
AND [o].[LocationId] IN ('00000000-0000-0000-0000-000000000000', '00000000-0000-0000-0000-000000000000')

For a single location id the query is now translated as

SELECT DISTINCT [o].[Year], [o].[TimeIdentifier]
FROM [Observation] AS [o]
WHERE [o].[SubjectId] = @__query_SubjectId_0
AND [o].[LocationId] = '00000000-0000-0000-0000-000000000000'

We will need to test this carefully as performance could be worse given that the constant location values in the SQL statement will result in unique query plans being generated as opposed to the previous parameterised version where the SQL statement remained constant.

Revert dependency downgrade made by #5002

This PR also reverts the changes made in #5002 which were going to downgrade EF 8.0.4 to 8.0.3 but this has not been deployed to any environment yet and is thought not be the cause of the degradation.