[DEV-15167] implement recipient lookup tool

[james-at-kc]

Description:

Search the recipients index in OpenSearch to find the most relevant results that can then be passed to the Advanced Search query. Cris may have insights from the filter semantic sessions for how to implement this filter.

Technical Details:

The lookup_recipient tool should look for matches on the following fields: recipient_name, uei, duns

The lookup_recipient tool returns a list of recipient names.

The tool should query the recipient OpenSearch index a single time to find a relevant match

Test cases are created to capture different scenarios for the filter, including the usage of fuzzy matching

Requirements for PR Merge:

1. Unit & integration tests updated
2. API documentation updated (examples listed below)
   1. API Contracts
   2. API UI
   3. Comments
3. Data validation completed (examples listed below)
   1. Does this work well with the current frontend? Or is the frontend aware of a needed change?
   2. Is performance impacted in the changes (e.g., API, pipeline, downloads, etc.)?
   3. Is the expected data returned with the expected format?
4. Appropriate Operations ticket(s) created
5. Jira Ticket(s)
   1. DEV-15167

Explain N/A in above checklist:

[zachflanders-frb]

I pulled this code down and tried it locally. The results seem good! I am requesting changes in order to

• use opensearchpy instead of elasticsearch_dsl library
• move the functions in recipient_retrieval into a helpers file in the tests directory
• Update the return value of the lookup tool to be a list of strings and remove the pydantic models from py_models (this one does not follow the pattern of the selectedLocations)

Additionally, it is my preference that we punt on the subcontractors lookup until later and potentially make it a separate tool, but would love others to weigh in on this too.