Change before and after filters in legal proximity search

[tmpayton]

Summary (required)

• Resolves Change the proximity filter term order #6127

This PR changes the meaning of the proximity_filter to mean that the proximity_filter_term comes before or after the q_proximity terms.

Required reviewers 1 - 2 developers

Impacted areas of the application

General components of the application that this PR will affect:

• legal search

How to test

• checkout this branch
• start elasticsearch ./elasticsearch
• pytest
• create case index: python cli.py create_index case_index
• load sample data for mur ) : python cli.py load_current_murs
• see test URLs below

Test URLs reference the following documents: MUR 8285

http://127.0.0.1:5000/v1/legal/search/?q_proximity=Dowell%20daunting&max_gaps=2&proximity_filter=after&proximity_filter_term=remediation

http://127.0.0.1:5000/v1/legal/search/?q_proximity=Dowell%20daunting&max_gaps=2&proximity_filter=before&proximity_filter_term=remediation

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.51%. Comparing base (6d7e30d) to head (06182ec).
Report is 2 commits behind head on release/public-20250211.

Additional details and impacted files

@@                     Coverage Diff                     @@
##           release/public-20250211    #6128      +/-   ##
===========================================================
- Coverage                    88.53%   88.51%   -0.03%     
===========================================================
  Files                           82       82              
  Lines                         9191     9191              
===========================================================
- Hits                          8137     8135       -2     
- Misses                        1054     1056       +2     

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

[fec-jli]

Test locally, it works as expected. Good job.
Thanks

[pkfec]

@tmpayton proximity_filter before/after works nicely.

[cnlucas]

Great job, @tmpayton