feat!: Pass HTTP resolvers to Signer::send_timestamp_request

[ok-nick]

This PR builds off the changes in #1846 to pass HTTP resolvers to the Signer::send_timestamp_request function. Our current code creates a new HTTP resolver on the fly for timestamping and doesn't respect the one contained in the resolver, this PR fixes that. It is step one to solving #1816, where we change the timestamp assertion code to call the signer function.

Note, some of the changes in #1846 are done here as well, so let's get that PR through first.

• Partially resolves Singer/AsyncSigner send_timestamp_request() method is not called for timestamping. #1816

[codspeed-hq]

Merging this PR will not alter performance

✅ 16 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing ok-nick/send-timestamp-request-respect (9e38bda) with main (d3488ec)²}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (a2ec0ea) during the generation of this report, so d3488ec was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[gpeacock]

Just a question about if you meant to keep commented out code.