fix(advance-filtering): handle error when columns are dynamically changed - 18.1.x

[georgianastasov]

Closes #14314

Additional information (check all that apply):

• [x] Bug fix
• [ ] New functionality
• [ ] Documentation
• [ ] Demos
• [ ] CI/CD

Checklist:

• [x] All relevant tags have been applied to this PR
• [x] 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

[ddincheva]

Since the PR to master with these changes is closed, I am leaving links to the comments and the remaining concerns here: https://github.com/IgniteUI/igniteui-angular/pull/14525#issuecomment-2242679103 https://github.com/IgniteUI/igniteui-angular/pull/14525#issuecomment-2245234690 Please log an issue with the new task regarding the UX experience when filtering is applied and the data of the grid is changed and link it here .. in order to have better tracking

[georgianastasov]

I have logged the new task regarding the UX experience when filtering is applied and the data of the grid is changed. You can track it here: #14595.