Implement cartesi coprocessor publish

[endersonmaia]

TBD

---

DRAFT

	- send the machine state to the solver
	- send car to ipfs (decide if we use ipfs public container or embed into cartesi/sdk)
	- check  :3034/ensure (SOLVER) if publish worked (healthcheck?)

[endersonmaia]

Should we also have a rollups publish to make the copy of the snapshot in a separate step, and have this deploy and publish steps aligned between coprocessor and rollups.

I think this way we give more visibility of what's happening, and also we can work towards an IPFS publishing the snapshot also for the rollups infrastructure.

[Nonnyjoe]

Yeahh.... @endersonmaia
I think splitting the current "rollups deploy" command into publish and deploy will actually create synergy between the coprocessor and the rollups development flow.

We can publish the machine snapshot in the publish step then deploy and register the necessary contracts like the application and authority in the deploy step.