Add observability operation

[diogopaulo]

Added a new parameter for the CC (-o) for observability purposes. This emits JSON events to stdout at key tunnel lifecycle points (starting, connected, disconnected, error). Each event is a single-line JSON object including destination hosts, connection status, and latency.

Generated outputs like

{
  "correlation_id":"550e8400-e29b-41d4-a716-446655440000",
  "time":1743033600.123,
  "host":"worker-01",
  "source":"outsystemscc",
  "sourcetype":"outsystemscc:tunnel",
  "event": {
    "version":"1.2.3",
    "event_type":"tunnel_starting",
    "server":"wss://pg.example.com/",
    "remotes":["R:8081:db.internal:5432"],
    "destination_hosts":["db.internal"],
    "status":"starting",
    "latency_ms":null,
    "error":null
  }
}

[diogopaulo]

Tagged as do not merge because it's the first time doing changes on the OS CC and want to understand if I am going on the right direction.

[wiz-code-outsystems]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	-
Sensitive Data	-
Secrets	-
IaC Misconfigurations	-
SAST Findings	-
Software Management Findings	-
Total	-

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

Pull Request Developer Guidance

Questions? See the Wiz FAQ.

Please contact the Security Office if you encounter issues with Wiz PR scanning.