Add optional sandbox ID to `miren logs` output for easier debugging

When running miren logs during debugging, it's difficult to determine which sandbox is producing which log lines. This makes it challenging to trace issues back to specific sandbox instances, especially when multiple sandboxes might be running.

Context from MIR-331: During the investigation of hanging downloads, it would have been helpful to see which specific sandbox (e.g., sb-CS88WuQqXjTRKboMxkUXe) was producing each log line when running miren logs to trace the issue.

Implementation:

• Add an optional flag (e.g., --include-sandbox-id or --verbose) to miren logs
• When enabled, prefix each log line with the sandbox ID
• Format could be: [sb-ABC123...] actual log message
• Should work with existing filtering and streaming functionality

Acceptance Criteria:

• miren logs --include-sandbox-id shows sandbox ID for each log line
• Flag works with existing log filtering options
• Sandbox ID format is consistent and easy to parse
• Default behavior (without flag) remains unchanged