[Issue #2775] Opportunity number partial match fix

[chouinar]

Summary

Fixes #2775

Time to review: 5 mins

Changes proposed

Adjusts the fields we query against and how in search

Context for reviewers

I wrote up a pretty thorough explanation of keyword vs non-keyword on #2775 - check that out. In short, the bug here is due to how the request/field being compared are tokenized. Keyword leaves a field "whole" and non-keyword tokenizes it into pieces. In the case of opportunity number splitting on each of the dashes (so ABC-123-XYZ becomes ["ABC", "123", "XYZ"]. In short, to support all the ways someone might want to query for an opportunity number, it's easiest to just include both.

Additional information

Some testing locally where I set the opportunity number to FY25-BSB-56789 and FY25-BSB-12345 for two opportunities:

[mdragon]

Nice, was hoping it would be that simple.