Add lastSearchInfo docs and unify interfaces with highlight directive- master

[onlyexeption]

Closes #13051

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

[PooSham]

@onlyexeption @kdinev @mtsvyatkova @igdmdimitrov This caused breaking changes in a minor release btw. We used matchInfoCache in our codebase and it stopped working. IMO you should re-add the old property ASAP and make a new PR that removes it in the next major release (according to this versioning system: https://github.com/IgniteUI/igniteui-angular/wiki/Ignite-UI-for-Angular-versioning)

Here is the breaking change
https://github.com/IgniteUI/igniteui-angular/pull/13286/files#diff-6dab3c2a71241663629e36dd675fefcf1f36396d74c66adbb1d9d4c7251de75eL106

[kdinev]

@PooSham I agree. @onlyexeption The breaking change was not checked in the checklist and I overlooked it during the review. Please add the property back in the 16.0.x branch and it can get removed in 16.1.x.

[kdinev]

@onlyexeption Actually, the PR should be reverted in 16.0.x and documented as a breaking change for 16.1.x. Please also see if you can add automatic migration for it.

[ChronosSF]

@onlyexeption @kdinev @mtsvyatkova @igdmdimitrov This caused breaking changes in a minor release btw. We used matchInfoCache in our codebase and it stopped working. IMO you should re-add the old property ASAP and make a new PR that removes it in the next major release (according to this versioning system: https://github.com/IgniteUI/igniteui-angular/wiki/Ignite-UI-for-Angular-versioning)

Here is the breaking change https://github.com/IgniteUI/igniteui-angular/pull/13286/files#diff-6dab3c2a71241663629e36dd675fefcf1f36396d74c66adbb1d9d4c7251de75eL106

@PooSham , 16.0.17 which was just released returns the matchInfoCache . We will probably revisit the API for 16.1 but it'll come with proper migrations. The change in a minor for 16.0 was not intended.