Merge bitcoindevkit/bdk#2182: fix: full_scan covers revealed range before applying...

Merge bitcoindevkit/bdk#2182: fix: full_scan covers revealed range before applying stop_gap

187b00747ab978a3bba21df5d14835ec31ed9fa3 test(esplora): allow(dead_code) at file level in common (Noah Joeris)
79d1f4501443559016de737fee8bdc572a99e248 fix: full_scan covers revealed range before applying stop_gap (Noah Joeris)

Pull request description:

  Fixes #2057. `full_scan` now always covers the revealed range before applying the stop_gap

  ### Notes to the reviewers

  Replaces #2181. That PR unified full_scan and sync into one path; per @evanlinjin's feedback we're keeping them separate and doing the minimal fix here instead

  ### Changelog notice

  Fixed: full_scan now always scans the full revealed range before applying stop_gap past last_revealed.

  ### Checklists

  #### All Submissions:

  * [x] I followed the [contribution guidelines](https://github.com/bitcoindevkit/bdk/blob/master/CONTRIBUTING.md)

  #### New Features:

  * [x] I've added tests for the new feature
  * [x] I've added docs for the new feature

  #### Bugfixes:

  * [ ] This pull request breaks the existing API
  * [x] I've added tests to reproduce the issue which are now passing
  * [x] I'm linking the issue being fixed by this PR

ACKs for top commit:
  evanlinjin:
    ACK 187b00747ab978a3bba21df5d14835ec31ed9fa3

Tree-SHA512: 9899e5d857d3cc3e86d35fd0e6a49204d4029053893b98fe1d8eb2bbdb9ea85b204997d87a72c9d485544286a0107936f048e54a7c152ab66b2106c897a1d900