Design a versioning mechanism for enclave/runner interface #443
Description
See this comment as an example that could have used such a versioning mechanism. Dan has a suggestion in the same thread above that I'm quoting here:
Shouldn't we have some explicit versioning in the runner/enclave interface so the runner and the enclave can negotiate whether they can successful run? Something like an API version that the runner can pass to the enclave, and the enclave can return an error if that API version isn't supported?