chore: cli: Confirm tooling that assumes knowledge of method params / returns don't break

[geoff-vball]

Related Issues

Closes #9776 (comment)

Proposed Changes

Tests the decoding the params/returns for InvokeContract and CreateExternal. These were the only new function calls I could find on hyperspace through filfox.

Additional Info

Checklist

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

• Commits have a clear commit message.
• 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, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[arajasek]

Thank you for this, it's good to see! Can we improve the tests to include actual assertions? I think we should be able to roundtrip the params in question, and use that for assertions. This might look something like:

• Defining a returnStruct

var dummyReturn Return {
	ActorID: 6491,
	RobustAddress: f275fpmqmhgj3zsfytktprbnftx7bojqyga3wyu5a (decoded from address)
	EthAddress    []byte{...the bytes}
}

• Marshaling that into a bytestr, which should give you the 8319195b5502ff4af64187327799171354df10b4b3bfc2e4c30654922d6956c99e12dfeb3224dea977d0939758a1fe string
• Then going through the process this test currently does, and comparing the return against dummyReturn