Execution tracing for past blocks

[Dentosal]

Requires VM PR FuelLabs/fuel-vm#881.

Description

Implements execution tracing for blocks/transactions that are already part of the chain state,and exposes this functionality through GraphQL. Also upgrades fuel-vm to not-yet-released 0.60.0.

Example query:

mutation {
  traceTx(
    txId: "1df52a41b46fcf1de387928ad1f2adf703d270ea9d4ad3e6c9fddd7f459a7a52",
    trigger: ON_RECEIPT
  ) {
    id, receipts {
      pc, reason, receiptType
    }, status {
      __typename
      ... on TraceSuccessStatus { executionTrace { receiptCount, registers, memoryDiff { start, bytes } } }
    }
  }
}

Heavily work-in-progress, needs:

• Decision on do we have this for whole blocks only, or single txs, or something more complicated
• Decision on WASM executor support
• Tests
• Docs

Checklist

• Breaking changes are clearly marked as such in the PR description and changelog: No breaking changes!
• New behavior is reflected in tests
• The specification matches the implemented behavior: This is outside spec scope.

Before requesting review

• I have reviewed the code myself
• I have created follow-up issues caused by this PR and linked them here

After merging, notify other teams

See the VM PR FuelLabs/fuel-vm#881.