fix(admin): validate execution id UUID format before making S3 request

[Guimove]

Summary

• Add UUID format validation on the execution id before sending the HTTP request
• Returns a clear error message with a hint to remove the timestamp suffix for cluster execution ids
• Remove the redundant info log that was shown after the 400 error (now surfaced upfront)

Test plan

• Run qovery admin download-s3-archive -e <uuid>-<timestamp> → should fail immediately with a clear error, no HTTP request made
• Run qovery admin download-s3-archive -e <valid-uuid> → should work as before