chore: added "Non Data Contact" toggle behavior to Generalized Search [CHI-2933]

[GPaoloni]

This PR is related to techmatters/flex-plugins#2512

Description

This PR adds support for it's UI counterpart, to add "Non Data Contact" toggle behavior to Generalized Search. To do so:

• Contacts mapping has been modified to include isDataContact boolean property (ElasticSearch).
• When the contact is indexed, we compute above property by using rawJson.callType.
• When a search is performed, we add an addition filter: if onlyDataContacts is present in the query, we add a filter clause to match only contacts that have isDataContact field set to true.

IMPORTANT ‼️
This changes require a complete reindex of all the documents.

Checklist

• Corresponding issue has been opened
• New tests added
• Feature flags / configuration added

Verification steps

• Indexing lambda is already deployed so you can skip this step.
• Deploy this branch to HRM development server. Alternatively you can run this branch locally, point to dev DB and ES instaces, but that might be more effort :P
• Start a new local Flex using this branch.
• After a search is performed, confirm that the "Non Data Contacts" toggle behaves as expected. Easiest way to do this is by checking that the amount of contacts greatly reduces if you set this toggle to true.
  • Ideally you can also check on HRM logs, where we are temporarily logging the search query, that it includes the appropriate filter on isDataContact field.

AFTER YOU MERGE

1. Cut a release tag using the GitHub workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

[mythilytm]

Thanks. I haven't tested but LGTM