feat: gas hook on ExecutionFinalResult

[shariffdev]

Closes #29

This approach as suggested by @ChaoticTempest does not add state to the worker and a hook can be offered instead, the the on_transaction method takes a hook that can collect the gas burnt information.

A GasMeter type is added with updated test code on how this all comes together to meter the gas burnt on doing asynchronous calls.

This approach allows to aggregate total_gas_burnt from all transactions that the Worker sees while transactions are being called.

[shariffdev]

@frol Since I can't invite reviewers currently, any comments from reviewers are welcome.

[frol]

@shariffdev I don't think it is what was described in the issue, see my comment there: #29 (comment)

[shariffdev]

Checking right now

@shariffdev I don't think it is what was described in the issue, see my comment there: #29 (comment)

[ChaoticTempest]

From what I see, this is only hooking onto the current transaction. We want to have the callback be executed on all transactions since the creation of the GasMeter. Worker here should still store a list of hooks so that it can call back on all of them whenever it receives a transaction result from the network. Sorry if my previous wording there didn't make sense.

What I suggest is to have a very similar API to Rust's Instant so that when it's created via GasMeter::now(&worker), it doesn't need to know about previous calls similar to the Instant::now API for time.

[shariffdev]

Hi @ChaoticTempest can you check this

[frol]

@shariffdev Please, make the CI pass. I see there is a dependency issue, use the following workaround: https://github.com/near/near-sdk-rs/pull/1075/files#diff-748c9b7c0e525461124dec4c258406a92d81a9b610f7b47a79efe9a0cb52553c

[shariffdev]

@frol The error is related to the clap requiring a newer rust version (1.70) I am looking into creating a new PR which we can update rustc to 1.70+, This issue seems to have been resolved so we can update to the latest 1.70+

[shariffdev]

This PR should take care of the dependency issue as we are using a newer stable toolchain

[ChaoticTempest]

Aside from the error unwrappings, this one is good to go

[frol]

@shariffdev Thanks for working on it and adding the documentation with an actionable example!