Feat: add deploy app log

[sonic-chain]

CP offers real-time display of pod running logs based on various space_uuids. Upon receiving a job, CP generates build_log_url and container_log_url, both of which are sent back to the server. The frontend utilizes these URLs to establish WebSocket objects and load the log data stream.

• CP receives a job, triggers app image building, and simultaneously stores log data as files during the build process. The resulting build log file's stream is returned as the WebSocket data source.
• CP retrieves the app pod log stream data associated with the space_uuid and sends it back by streaming through WebSocket.
• On the CP end, it monitors WebSocket client connections for closure events. When such an event occurs, CP discontinues fetching log data and releases the connection.

[Normalnoise]

@PlutoNbai please leave your comment about the CP log to Lagrange server and web.

[Normalnoise]

we can refer the similar design

[sonic-chain]

The new features have been developed in this branch: https://github.com/sonic-chain/go-computing-provider/tree/feat-cp-logs

[sonic-chain]

Use case:

• build image log

  ws://[publicIp]:[port]/api/v1/computing/lagrange/spaces/log?space_id=xxxx&type=build

• pod log

  ws://[publicIp]:[port]/api/v1/computing/lagrange/spaces/log?space_id=xxxx&type=container