fix: fvm: make exectraces match legacyVM some more

[arajasek]

Related Issues

@jennijuju pointed out that the top-level message in the FVM exectrace deviates from the LegacyVM -- it uses resolved (ID) addresses, and excludes some of the information packaged in the message receipt.

Proposed Changes

Match LegacyVM behaviour by setting the top-level message & rct from the receipt itself, not the exectrace.

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

• All commits have a clear commit message.
• The PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, INTERFACE BREAKING CHANGE, CONSENSUS BREAKING, build, chore, ci, docs,perf, refactor, revert, style, test
  • area: api, chain, state, vm, data transfer, market, mempool, message, block production, multisig, networking, paychan, proving, sealing, wallet, deps
• This PR has tests for new functionality or change in behaviour
• If new user-facing features are introduced, clear usage guidelines and / or documentation updates should be included in https://lotus.filecoin.io or Discussion Tutorials.
• CI is green