take advantage of new workspace hierarchies to split out "sapio core" workspace from host stuff

[JeremyRubin]

No description provided.

[ProofOfKeags]

Is this solely for dev environment stuff or am I misunderstanding "workspace" in this context?

[JeremyRubin]

Cargo.toml can have a [workspace] and then interpret subdirectories as part of one logical target.

IIRC theres some recently improved support for having a workspace-of-workspaces.

we could split sapio into a core workspace and a non-core workspace. Core can be all the things required to author a contract, non-core can be things required to run a contract.

splitting things like this makes it much simpler to ensure that we have a minimal set of dependencies and flags set for contract authors, and can also help improve compile times when used as a submodule if you an just pull in one sub-workspace.