feat: shared quartz_common crate + enclave server macro

[dangush]

Closes #81

Moved quartz-cw, quartz-enclave, and quartz-proto into:

quartz_common::{contract, enclave, proto}

Also created quartz_server! macro to cut down enclave/main.rs boilerplate down to 1 line:

cycles-quartz/apps/mtcs/enclave/src/main.rs

Lines 26 to 30 in c3cbd80

	// Passing a custom clap Cli is optional
	quartz_server!(Cli, MtcsServer, |sk| MtcsServer::new(MtcsService::new(sk, EpidAttestor)));
	// With default Cli:
	// quartz_server!(MtcsServer, |sk| MtcsServer::new(MtcsService::new(sk, EpidAttestor)));

Acceptance Criteria

This PR is ready when:

• proto related bugs are fixed
• the MTCS server runs
• handshake performs
  • requires merging with other branches but idt it's affected anyway, quartz macro can receive another look-over

TODO

We don't need quartz relayer here right?

[davekaj]

Left some comments. Also when I tried to run in MOCK_SGX mode for the transfer app, I got this error:

QUARTZ_PORT is set to: 11090
set trusted hash
... 09E63DFD91ECD4394ABF3D7222AAF60D49253549C19B650B31DCFF722C2B934F
MOCK_SGX is set. Running enclave without gramine...
Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }

Did you also get this error? If you don't have it, then it must be my environment. But if you have it as well, it might be an error related to one of my comments below, or something else

[hu55a1n1]

Nice work! I did preliminary review and added some comments.
Nit: Cargo.tomls are not formatted and deps are not alphabetically ordered 😅. (feel free to ignore)
Haven't tested yet - just want to make sure mock-sgx is working correctly but will wait for the fix for using DefaultAttestor in the enclaves. Will try to test tonight otherwise will delegate to the team (because I'm off for the rest of the week). 🙏

[hu55a1n1]

I think the macro is cool, but I am not convinced we need it for the following reasons -

• The main reason to have this macro IMHO would be to make sure the user/dev didn't forget to add the quartz CoreService. But I think there are other ways to achieve that. e.g. ->

trait QuartzServerExt {
    fn quartz_builder(
        config: Config,
        sk: Arc<Mutex<Option<SigningKey>>>,
        attestor: DefaultAttestor,
    ) -> Router;
}

impl QuartzServerExt for Server {
    fn quartz_builder(
        config: Config,
        sk: Arc<Mutex<Option<SigningKey>>>,
        attestor: DefaultAttestor,
    ) -> Router {
        Server::builder().add_service(CoreServer::new(CoreService::new(
            config,
            sk.clone(),
            attestor.clone(),
        )))
    }
}

• The macro does reduce the amount of code to be written but users might want the flexibility to specify their own config e.g. light client opts, etc.
• Users may also want to add more services.
• The macro is restricting users ability to use their libs of choice e.g. for CLI, tokio, etc. (I don't think we should make such decisions on their behalf)

[hu55a1n1]

Superseded by #123 (which has been merged already).