Add EF.Functions.JsonExists(expression, path) DbFunction

[mseada94]

• Fixes Relational method for checking whether a path in a JSON exists #31136

• I've read the guidelines for contributing and seen the walkthrough
• I've posted a comment on an issue with a detailed description of how I am planning to contribute and got approval from a member of the team
• The code builds and tests pass locally (also verified by our automated build checks)
• Commit messages follow this format:

        Summary of the changes
        - Detail 1
        - Detail 2

        Fixes #bugnumber

• Tests for the changes have been added (for bug fixes / features)
• Code follows the same patterns and style as existing code in this repo

TODO

• Define relational level EF.Functions.JsonExists DbFunction
• Define SqlServer translation
• Define Sqllite translation
• Add test for constant json expression translation success
• Add test for column (string) json expression translation success
• Add test for column (owned) json expression translation success
• Add test for column (string value converter) json expression translation success
• Add test for column (not of the previous types) json expression translation failure
• Add function test for 3 cases of the result (true, false, null)

Design notes:

• The json expression is being tested before translation to allows only
  • String expressions (column, constant, complex)
  • Owned JSON column expression
  • Column with string value converter expression
• In SQL Server, EF.Functions.JsonExists translate to JSON_PATH_EXISTS function which require SQL Server 2022.
• In SQLite, EF.Functions.JsonExists translate to the following expression using JSON_TYPE function, as the best available equivalent for JsonExists at the moment.
  IIF(arguments_0 IS NULL, NULL, JSON_TYPE(arguments_0, arguments_1) IS NOT NULL)

CASE 
    WHEN arguments_0 IS NOT NULL THEN JSONT_YPE(arguments_0, arguments_1) IS NOT NULL
    -- no need to this line as default of case else result is null (ELSE NULL)
END

• The nullability of the second argument is not considered, generally user should not use null json path when calling this function
  • In SQL Server there will be an error
  • In SQLite JSON_TYPE will return NULL which will result in FALSE to be returned from this expression

[mseada94]

Sorry for taking to long with no updates, I faced some issues when writing the tests and I did not have the time to check them.

I fixed some of the translation code and used object datatype instead of generic which fail early and did not let the method translator to be called.

I had issue with SqlServer Compatibility Level, It was configured on the fixtures but the localdb on my device was not the latest version and it took me some time to figure it out.

There is some other issues:
1- The owned json column is failed on the translation before reaching the method translator on the argument visit check as the argument of type RelationalStructuralTypeShaperExpression, I am not sure how to handle this issue please your advice.
2- The Result asserting try to filter the data on memory to compare the results, while I did not add memory implementation for the method, I will check how the assertion is working and avoid memory translation if possible.

[roji]

@mseada94 no problem; when you feel the PR is ready for review, flag it as such and we'll take a look.

[mseada94]

@roji I was able to fix all issues, just the owned json property still not sure how to handler it and deal with the property as ColumnExpression instead of RelationalStructuralTypeShaperExpression

The owned property serialization and deserialization should be handled by the framework and it supports translating normal expressions so there is no need for using functions such as JsonExists nor JsonValue.

Should I ignore this case based on that?