Investigate and start to charge for storage artifacts produced by transactions

[xgreenx]

Problem overview

Each transaction leaves disk space delta after execution like:

• Inserting a new K/V into a state or asset into balances also has Sparse Merkle Tree storage overhead.
• Contract's bytecode occupies the Transactions and ContractsRawCode tables.

Solution

The fuzzing tool https://github.com/FuelLabs/fuel-core/issues/1402 can help us identify other artifacts produced by transaction fields/operations.

In the end, we need to charge the user for these artifacts as part of:

• The opcode price https://github.com/FuelLabs/fuel-vm/issues/602
• Witness data https://github.com/FuelLabs/fuel-core/issues/1161
• As an additional part to min_fee.

Acceptence criteria

Prove that we handled charging for storage artifacts in other issues. If not, we must create a new sub-issue to track the progress.

We can close this issue when all sub-issues are solved.