Call markForCheck when filter chip is clicked

[mtsvyatkova]

Closes #16903

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

[mtsvyatkova]

Without prior state restoration, the bug is hard to reproduce because Angular's event binding on the chip click calls markForCheck() on the filter cell component, and the dirty flag propagation reaches the header row (I cannot reproduce it without the setState call).

However, after setState(), setStateInternal calls this.grid.cdr.detectChanges() synchronously (line 558 in state-base.directive.ts, marked with // TODO). This forces a full check of the grid subtree, clearing all OnPush dirty flags. After that, the event binding's markForCheck() starting from the filter cell no longer reliably reaches the header row, and isFilterRowVisible is never re-evaluated (line 112 in grid-header-row.component.html).