feat: Add cvm reverse proxy client and server side

[MoeMahhouk]

No description provided.

[MoeMahhouk]

This is just a draft and not final way.
I am thinking to provide the recipes to build the binaries and have different recipes in the meta-evm layer for the init scripts where we start them because I am not sure if it is relevant for the base TDX images to start those two server and client side CVM reverse proxies. But we can discuss this in the team together.

[metachris]

that one is for public access, proxying to orderflow-proxy?

if so, then it should:

1. listen on port 7936
2. proxy to localhost:14727

[MoeMahhouk]

Why have a separate cvm server proxy for the orderflow-proxy and not have them built in a single one directly?
are there any other purposes for the cvm-reverse-proxy-server beside forwarding to the orderflow proxy?

[metachris]

• one receives a request from outside and forwards it to the local orderflow-proxy service
• the other receives a request from orderflow-proxy or rbuilder, and forwards it to BuilderHub

[MoeMahhouk]

I meant only about the orderflow proxy and cvm-reverse-proxy server. Why separate them instead of have them both in one?

[metachris]

where is the version pinned?

[MoeMahhouk]

This is currently a dev instance which is taking the up-to-date version of the cvm-reverse-proxy.
See line 14, SRCREV = "${AUTOREV}".
If we have a fixed version, we should change SRCREV to point to that exact tag/commit hash.

The AUTOREV placeholder takes automatically the latest commit of the repo and builds it.