refactor: cleaning up RuntimeConfig

[jakmeier]

refactor: cleaning up RuntimeConfig

Sorry. This is a humongous change.
But it's really just a lot of the same boilerplate code changes.

The key changes are:

• Action fees are now accessed through one single function
  RuntimeFeesConfig::fee(&self, cost: ActionCosts) instead of
  selecting a specific field deep down in the structure
• Action fees are stored in an EnumMap instead of by hard-coded fields
• The JSON RPC now has RuntimeConfigView to keep compatibility
• Creation of RuntimeConfig no longer goes thorough serde JSON
  serialization + deserialization

The goal of this PR is to make gas profiling based on parameters
possible, which in turn makes parameter weights possible to implement
much more easily. The key here is that we no longer have to lookup the
gas value up independently from the profile key.

Today:

self.gas_counter.pay_action_base(
    &self.fees_config.action_creation_config.deploy_contract_cost,
    sir,
    ActionCosts::deploy_contract_base,
)?;

After PR:

self.pay_action_base(ActionCosts::deploy_contract_base, sir)?;

Also it gives us simplified fee lookup on RuntimeFeesConfig.
Before, we need things like:

let exec_gas = self.cfg.action_receipt_creation_config.exec_fee()
    + self.cfg.action_creation_config.add_key_cost.function_call_cost.exec_fee()
    + num_bytes
        * self
            .cfg
            .action_creation_config
            .add_key_cost
            .function_call_cost_per_byte
            .exec_fee();

which becomes

let exec_gas = self.cfg.fee(ActionCosts::new_action_receipt).exec_fee()
    + self.cfg.fee(ActionCosts::add_function_call_key_base).exec_fee()
     + num_bytes * self.cfg.fee(ActionCosts::add_function_call_key_byte).exec_fee();

The final state after all refactoring is done is described in #8033.
This PR contains step 2 and 4 combined because I was not able to
separate them due to unforeseen dependencies we have in the code.

The hardest part should be done after the current PR and what follows
should be small PRs that get rid of types one by one.

Test

We have to make sure this is a pure refactoring change without
side-effects. Luckily, we have test_json_unchanged that detects
changes in any protocol version.
Otherwise, we rely on tests that have gas profile snapshots to make
sure the gas fee lookup translation did not have errors.

[Longarithm]

Looks great! I hope there are no incorrectly replaced costs or mixed send and exec fees, though I looked at this. On the other hand, our tests should cover this.