Correct delete search param workflow

[SergeyGaluzo]

Fixes https://microsofthealth.visualstudio.com/Health/_workitems/edit/190743
User story has good explanation.
As far as implementation, I decided to keep as much of current pipeline logic as possible and remove resources from being deleted at the last stage in merge. Now, merge does not include resources for search params with pending delete and pending hard delete statuses.
I also decided to temporarily keep current logic to find resources for URLs based on full search param scan (handles current logic when resource deletes happen in the same SQL transaction with status updated). This should cover cases when current pending deletes are not yet processed by reindex. I will remove this fallback later when new logic lives in PROD for a while.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.90%. Comparing base (5f350b6) to head (51c416f).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5629      +/-   ##
==========================================
+ Coverage   76.89%   76.90%   +0.01%     
==========================================
  Files         997      997              
  Lines       36617    36724     +107     
  Branches     5529     5544      +15     
==========================================
+ Hits        28155    28243      +88     
- Misses       7113     7128      +15     
- Partials     1349     1353       +4     

see 21 files with indirect coverage changes

🚀 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.

[SergeyGaluzo]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).