Bug 1897264 - interruption support for ingestion (backport #6246)

[mergify]

Added an interrupt_everything method that interrupts both the read and write connection. This is intended for iOS to use to interrupt the suggest component during shutdown. See https://bugzilla.mozilla.org/show_bug.cgi?id=1897299 for a discussion on next steps here.

Created a new WriteScope type that stores an interrupt scope that can be used for multiple write calls. This allows the ingestion code to catch all interruptions that happened after the ingestion started. With the old system, if interrupt_everything was called in-between ingestion two types then we might miss it.

Pull Request checklist

• Breaking changes: This PR follows our breaking change policy
  • This PR follows the breaking change policy:
    • This PR has no breaking API changes, or
    • There are corresponding PRs for our consumer applications that resolve the breaking changes and have been approved
• Quality: This PR builds and tests run cleanly
  • Note:
    • For changes that need extra cross-platform testing, consider adding [ci full] to the PR title.
    • If this pull request includes a breaking change, consider cutting a new release after merging.
• Tests: This PR includes thorough tests or an explanation of why it does not
• Changelog: This PR includes a changelog entry in CHANGELOG.md or an explanation of why it does not need one
  • Any breaking changes to Swift or Kotlin binding APIs are noted explicitly
• Dependencies: This PR follows our dependency management guidelines
  • Any new dependencies are accompanied by a summary of the due diligence applied in selecting them.

Branch builds: add [firefox-android: branch-name] to the PR title.

---

This is an automatic backport of pull request #6246 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 8bd7ba4 has failed:

On branch mergify/bp/release-v127/pr-6246
Your branch is up to date with 'origin/release-v127'.

You are currently cherry-picking commit 8bd7ba4ea.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   components/suggest/README.md
	modified:   components/suggest/src/suggest.udl

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   components/suggest/src/db.rs
	both modified:   components/suggest/src/lib.rs
	both modified:   components/suggest/src/store.rs

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 50.85%. Comparing base (5e7b702) to head (c97e7ec).

Additional details and impacted files

@@                Coverage Diff                @@
##           release-v127    #6256       +/-   ##
=================================================
- Coverage         83.68%   50.85%   -32.84%     
=================================================
  Files               117      112        -5     
  Lines             15653    11811     -3842     
=================================================
- Hits              13099     6006     -7093     
- Misses             2554     5805     +3251     

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

[linabutler]

Alrighty—I backported #6236 as part of this PR, too, because it was a lot easier to rebase #6246 atop it! 😅

@bendk Would you mind double-checking this just in case, please, before I request uplift? Thanks!

[bendk]

Looks great to me, thanks for doing this uplift.

[linabutler]

The SwiftLint failures aren't caused by this PR (but, unfortunately, that means it's failing on all our PRs now)—#6254 fixes them for everyone!