Throw when exists() combined with CASE

[as51340]

Closes #1376
Out current architecture doesn't allow combining exists with anything except filtering because we would have to combine rule based planner with evaluation. Hence, current best solution is to explicitly throw (better than returning wrong results).

[master < Epic] PR

• Check, and update documentation if necessary
• Write E2E tests
• Compare the benchmarking results between the master branch and the Epic branch
• Provide the full content or a guide for the final git message

[master < Task] PR

• Check, and update documentation if necessary
• Provide the full content or a guide for the final git message

To keep docs changelog up to date, one more thing to do:

• Write a release note here, including added/changed clauses
• Tag someone from docs team in the comments

[as51340]

Changelog: When using exists within CASE, utils::NotYetImplemented exception will be thrown.