Setup CI/CD

[wyc]

• Compilation checks
• Unit testing
• Integration testing

[clehner]

What would be deployed/delivered in CD?

• Publishing to crates.io? Or should that be done manually by maintainers?
• Publishing binary builds? (to GitHub?) Currently we just have a library here, no executable - besides the vc-test-suite test driver. I think if people are using the Rust library, they would be using cargo, which would build the library from source anyway. But binaries could be useful for if we are building a C-ABI shared library and/or bindings to other languages (re: Architect FFI to support porting into other languages and platforms, including Android/iOS #10).
• Project website? Or use GitHub pages?

[wyc]

I think passing the vc-test-suite as part of our CD would be a great outcome. Perhaps we could publish the test binary to break ground on how other binaries should happen? At this point we may have to revisit key mgmt strategies as a company.

We should have a longer discussion about this, will reach out to get some time.

[clehner]

@wyc I opened #26 for an implementation of the CI part. Can defer to later discussion if you prefer.