feat: add --service-id flag to qovery log command

[Guimove]

Summary

• Adds --service-id flag to qovery log that accepts a service UUID directly
• Bypasses all name→ID API resolution (no listing of applications, containers, jobs, etc.)
• Compatible with the existing context flow — org/project/environment are still resolved normally, only the service lookup is skipped

Motivation

When working from a Qovery console URL, the service UUID is immediately available in the path (e.g. .../service/9243f628-0c88-440f-9c4a-39b961650b7b/service-logs). Previously, the CLI required the service name instead, forcing an extra lookup. This flag eliminates that round-trip for agentic and scripted workflows.

Usage

qovery log --service-id "9243f628-0c88-440f-9c4a-39b961650b7b"

Test plan

• Built and tested locally against a live service — logs streamed correctly with the UUID
• Existing name-based flags (--service, --application, etc.) are unaffected
• --service-id case is evaluated first in the switch, so it takes priority when provided