feat: nonce filling layer

[onbjerg]

Motivation

This is a replacement for NonceManagerMiddleware in ethers

Solution

A layer that fills nonces for transaction requests. It does not require you to specify a sender address like in ethers, instead we use a dashmap internally.

I would like some ideas on how to test that this works with sending transaction requests for the same sender from multiple threads at the same time (i.e. a sanity check on the atomics)

Closes #275

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[mattsse]

smol derive nit, lgtm otherwise

[mattsse]

• debug + clone etc

[zerosnacks]

@onbjerg could it be that the ManagedNonceLayer doesn't track contract deployments? I'm getting some strange errors where at once it complains that either the nonce is too high (1) or too low (0) after deploying a contract with the same provider.

For context see: https://github.com/alloy-rs/examples/pull/20/files

[onbjerg]

It should provided the function you use to deploy uses send_transaction. Where exactly are you getting the error?

[zerosnacks]

It should provided the function you use to deploy uses send_transaction. Where exactly are you getting the error?

I've opened an issue on Alloy to explore this with a minimal reproduction example: #406 + https://github.com/zerosnacks/alloy-repro-406