Use gas profiles everywhere

[jakmeier]

Gas profiles are a nearcore internal concept. It is not reflected on chain and is not observable on the protocol level.

The use of gas profiles so far is just for the RPC methods, so they can provide a detailed break down of gas costs on tx-status calls. I think they are also used by tooling for smart contract developers, so they can compare gas costs across code changes.

AFAIR, profiles currently are only collected for function calls. It's definitely not collected for transaction to receipt conversion. But I am not sure about action receipt execution for actions that are not function calls.

The goal of this issue is to always collect gas profiles. This would allow to use gas profile for a bunch of new use cases:

• Use it to display undercharging metrics on Grafana (Metrics that show gas weight multiplied gas consumption vs compute time #8258)
• Analysis for how a gas parameter change would affect old traffic.
• Better smart contract tooling.