Feat: K8s docker devOps support

[smtmfft]

Describe the feature request

To enable k8s support for prover devOps.

• k8s deployment config: @johntaiko
  • deploy on tx cloud the 1st.
  • link with in-k8s node for better performance
  • need a workflow for k8s image upgrade
• automatically register sgx id in raiko @smtmfft
  • checking bootstrap readiness.
  • call addInstance() abi in raiko
  • refactor D::run() to d = D::new() && d.run() for per instance status storage.
• open apis for healthy & performance @petarvujovic98
  • open API refactory: Proverd openapi #31
  • open api document for client to integrate.
  • (optional): Can we make current api neat-er? i.e. use {prover_type, prover_args: {arg1, arg2}} instead of current {prover_type, prover_args: {prover_type:{arg1, arg2}}}. I think as the type is parsed above, no need to set another key level inside prover_args.
  • error message refactory, to avoid errors like: raiko panicked #158 & Broken Pipe errors #154
• miscs

Spam policy

• I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

[petarvujovic98]

@smtmfft I'll start refactoring the error messages throughout the host and the guests after that to make them more readable and informative.