Implement advanced search

[d-buchmann]

Supersedes PR #944
Nota bene: Test were generated using AI. The actual code is handwritten.

Up to 5 individual tokens (separated by spaces) can be given as search string. Each token is individually searched for in all selected fields.

Examples (assuming the relevant fields are selected for search):

• a part named foo with a tag bar will be found with the search string "foo bar".
• a part named bar baz will be found with the search string "baz bar".
• A capacitor named MLCC 100nF, Manufacturer Kemet, Footprint 0603 will be found with any combination of the 4 keywords in any order.

All above examples don't yield these results in the current search implementation.
While the filter would be the more efficient tool to achieve the same results, some users might not be familiar with this - but quite possibly with a search bar.

Added SearchSettings which has 3 items:

• Enable advanced search (or else fall back to the current behavior)
• Search token count (default 3, range 2-5), limits the query size/complexity
• Configurable behavior of wildcards (search, % as a wildcard works inconsistently #1355)

[codecov]

Codecov Report

❌ Patch coverage is 93.33333% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 58.49%. Comparing base (57a0dfd) to head (2a1c985).
⚠️ Report is 54 commits behind head on master.

Files with missing lines	Patch %	Lines
src/DataTables/Filters/PartSearchFilter.php	93.02%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1406      +/-   ##
============================================
+ Coverage     58.44%   58.49%   +0.05%     
- Complexity     8667     8687      +20     
============================================
  Files           634      637       +3     
  Lines         27991    28070      +79     
============================================
+ Hits          16359    16420      +61     
- Misses        11632    11650      +18     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jbtronics]

I took a rough look:

• I think its not so useful to make this search mode global behavior, but instead user configurable (via the existing search options dropdown). This also allows to temporarily switch it. Maybe the system settings can stay as some default
• Is there much need to make the token count configurable? Is there much disadvantage than just hardcode it to 5 or so? Its probably rare that someone use so many token anyway, and the worst that can happen is that the search request takes a bit longer, but you can still use a different search mode for this.

[d-buchmann]

You're right about the user configurability, that way it can adapt to the varying user preferences much better.
I also hardcoded the token count to 5 which is indeed plenty and threw out the search settings completely because that would have overcomplicated it.

Meanwhile advanced search sounds odd to me, so I used the term extensive which describes better what it does - it just searches "more", not necessarily "better".

One more aspect I haven't yet solved is that regex and extensive search are mutually exclusive in the PHP code, but not in the user interface. It works, but if regex is enabled, the other two options will be silently ignored.