Use latest gas price to estimate next price for tx pool checks

[MitchTurner]

Linked Issues/PRs

Description

There are 3 services that rely on the gas price: producer, tx pool, and graphql. In 0.41.0, graphql used the latest block, but the producer and tx pool use the actual next gas price.

This works great on the producer node, but for all the sentries that also have tx pools they need to be perfectly in sync with the block producer or else the expected gas prices will be different.

The new change has the tx pool behave the same as graphql, where it has access to the latest block and can calculate the (worst case) gas price for the next block.

This is already what the end users are doing to set a max fee on their tx, so it shouldn't exclude any txs that should be in there.

Sentries will reject txs if they don't have the correct parameters, this solves this problem by using the "worst case" for next gas price based on the the latest actual block.

Checklist

• New behavior is reflected in tests

[xgreenx]

What gas price do we use during dry run as a default gas price?

[MitchTurner]

What gas price do we use during dry run as a default gas price?

It uses the same value as the producer, unfortunately:

        let gas_price = if let Some(inner) = gas_price {
            inner
        } else {
            self.calculate_gas_price().await?
        };

Does anyone use the default value?

[xgreenx]

We provide this functionality, so we need to guarantee it to work=D Looks like it uses gas price service. I think we need to change it to use value based on the previous block

[MitchTurner]

We provide this functionality, so we need to guarantee it to work=D Looks like it uses gas price service. I think we need to change it to use value based on the previous block

K. I'll create a PR.

[rafal-ch]

LGTM 👍