First iteration of user-defined IPC actors

[adlrocha]

This issue tracks the main issues and PRs to be closed in order to have a first iteration of IPC's user-defined actors. When this milestone is reached we would be in a good place to start the integration with Lotus:

• ipc-subnet-actor:

  • Use TCid instead of Cid throughout the actor ipc-subnet-actor#3: This one is being addressed by @cryptoAtwill through this PR and the follow-ups.
  • Unit test leveraging fvm_utils::MockRuntime: Now that we have decoupled the runtime abstraction from builtin-actors into fvm_utils we can perform proper tests over the subnet_actors (which wasn't the case before): Support checkpoint ipc-subnet-actor#9

• ipc_atomic_exec:

  • Take this PR to the finish-line. Before merging we should consider including a few tests to see that it works and then include the full coverage.
  • Unit tests leveraging fvm_utils::MockRuntime: Unit test coverage ipc-atomic-execution#2. We can probably migrate directly the ones included here
  • Migrate this PR to ipc_atomic_exec and consider merging it as an improved implementation of the atomic_exec protocol.
  • Sample actor supporting atomic execution: Sample actor supporting atomic execution. ipc-atomic-execution#5

• ipc_gateway

  • Break actor code into smaller actors #3: Being addressed with the decoupling of the atomic execution protocol to its own actor.
  • Migrate unit-tests from builtin-actors/actors/hierarchical-sca to ipc-gateway.

• ipc_sdk

  • Extract common IPC types (IPCAddress, SubnetID, etc.) into its own repo and start working on an ipc sdk (see for context Common library crate for both ipc and atmoic-execution ipc-atomic-execution#3)
  • Implementation of an interface detection (to be able to detect actor types in the interaction between IPC actors): Verify caller type #2

• All actors are deployable leveraging lotus::experimental/fvm-m2 branch, and we can interact with them.

  • Create client to interact with actor: https://github.com/consensus-shipyard/ipc-subnet-actor-client/issues/1

• Populate READMEs for all actors:

  • https://github.com/consensus-shipyard/ipc-gateway
  • https://github.com/consensus-shipyard/ipc-subnet-actor
  • https://github.com/consensus-shipyard/ipc-atomic-execution
  • https://github.com/consensus-shipyard/fvm-utils

All the above issues are also addressing the "great renaming": consensus-shipyard/ipc-subnet-actor#5.

As mentioned by @cryptoAtwill below, support for native actors have been removed momentarily from ref-fvm and experimental/fvm-m2. The working versions of ref-fvm and lotus to make the actors work so far are:
lotus commit: c602412eba07c3e5650b6ebd59d93f640411ee1b
fvm_*: 3.0.0.alpha.5

[cryptoAtwill]

For this version, so far the working combination of each component is as follows:
lotus commit: c602412eba07c3e5650b6ebd59d93f640411ee1b
fvm_*: 3.0.0.alpha.5

[adlrocha]

This issue has been mostly addressed. Closing in favor of IPC M2 issues