fix(connector-besu): invokeContractV2 replacement transaction underpriced

[petermetz]

Describe the bug

https://github.com/hyperledger/cactus/pull/684/checks?check_run_id=2223081488#step:15:950

I know this PR is unrelated, but that test failure looks like a randomly occurring flake in the nonce handling2 probably due to race conditions (just a guess).
What I confirmed so far is that the test works on my machine, but it failed while being executed by the CI (usually the CI is good at catching race conditions because it's slow.

To Reproduce

It appears to be flaky or only happen on weaker hardware under heavy load, not sure.

Expected behavior

Test should pass consistently.

Logs/Stack traces

https://github.com/hyperledger/cactus/pull/684/checks?check_run_id=2223081488#step:15:950

Screenshots

N/A

Cloud provider or hardware configuration:

CI

Operating system name, version, build:

N/A

Hyperledger Cactus release version or commit (git rev-parse --short HEAD):

main

Hyperledger Cactus Plugins/Connectors Used

Besu. I suspect that Quorum may also be affected, but who knows.

Additional context

This came up randomly after rebasing Jagpreet's prometheus PR to upstream/main. I'm assuming that the monitoring code does not have any side effects on the rest of the connector logic, but this could also turn out to be false of course.

cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo @jagpreetsinghsasan

[petermetz]

Never seen the flake again so closing this one. Will open a follow-up task to design a nonce manager.