feature: Get compute usage from profile

[aborg-dev]

This seemed like the simplest approach that introduced minimal runtime overhead and code changes (as opposed to introducing a dedicated field in the GasCounter). Happy to consider the alternatives though.

Part of #8032

Some follow-up work is planned in #8795

[jakmeier]

Looks good. Going through gas profiles seems like the best way to me, too. For actions, we will either have to make profiles more general, or perhaps add the compute cost counter for it (on the receipt level) after all.

Just one question, is there a way we can ensure the values in the gas profile are always the same as in the gas counter? Because today profiles are a mere debug tool and we wouldn't necessarily know it it is slightly wrong in some cases. But once compute cost limits are fully implemented, this makes it part of the protocol specification. Any bugs we would find later would require a protocol update to fix.

[aborg-dev]

Just one question, is there a way we can ensure the values in the gas profile are always the same as in the gas counter? Because today profiles are a mere debug tool and we wouldn't necessarily know it it is slightly wrong in some cases. But once compute cost limits are fully implemented, this makes it part of the protocol specification. Any bugs we would find later would require a protocol update to fix.

I've added a test in gas_counter.rs that verifies that the compute usage in Profile agrees with the burnt gas in the counter. Another way to achieve this would be to track the counters in the gas counter itself and them export them to Profile and to Compute Usage calculation. That probably is a cleaner solution in the long-run, though requires more work. I'll see if I can reuse/replace EXT_COSTS_COUNTER while doing this.

Will file an Issue to track this work.
UPD: I've filed an issue for this #8795.