Grid validate filtering expressions tree

[hanastasov]

Closes #15563

Additional information (check all that apply):

• Bug fix
• New functionality
• Documentation
• Demos
• CI/CD

Checklist:

• All relevant tags have been applied to this PR
• This PR includes unit tests covering all the new code (test guidelines)
• This PR includes API docs for newly added methods/properties (api docs guidelines)
• This PR includes feature/README.MD updates for the feature docs
• This PR includes general feature table updates in the root README.MD
• This PR includes CHANGELOG.MD updates for newly added functionality
• This PR contains breaking changes
• This PR includes ng update migrations for the breaking changes (migrations guidelines)
• This PR includes behavioral changes and the feature specification has been updated with them

[gedinakova]

@Otixa Hristo's scenario is actually a little different. The idea is that we may have a scenario in which a grid field is, let's say, no longer available. This would lead to breaking the user's app because the expression tree has not been checked & updated accordingly. Maybe it's not that bad to simply show an empty grid which would hint them into the direction there's something wrong with the filters.

[hanastasov]

Oh i;m such a rookie - fix should be "

        if (expr.condition.logic) {
            return expr.condition?.logic(val, expr.searchVal, expr.ignoreCase);
        }

will make a new pr #15568