bug: service connection --subnets docs show unsupported comma-separated format

[cdot65]

Overview

The service connection docs show --subnets "10.1.0.0/24,10.1.1.0/24" (comma-separated in a single string), but the API rejects this with INVALID_IPSPEC_SUBNET. The correct usage is repeating the flag: --subnets 10.1.0.0/24 --subnets 10.1.1.0/24.

Context

• File: docs/cli/deployment/service-connection.md line 54
• Command: src/scm_cli/commands/deployment.py line 523
• The --subnets option is typed as list[str] (Typer repeatable option)
• Comma-separated string passes through as a single list element, API rejects it

Steps to Reproduce

# This fails with INVALID_IPSPEC_SUBNET
scm set sase service-connection --name test --ipsec-tunnel tun1 --region us-east-1 --subnets "10.1.0.0/24,10.1.1.0/24"

# This works
scm set sase service-connection --name test --ipsec-tunnel tun1 --region us-east-1 --subnets 10.1.0.0/24 --subnets 10.1.1.0/24

Fix Options

1. Fix docs to show repeated --subnets flags (quick fix)
2. Fix CLI to split comma-separated input into list elements (better UX, matches docs)
3. Both

Acceptance Criteria

• Docs examples use correct syntax
• OR: CLI splits comma-separated subnets before sending to API
• Whichever approach is chosen, docs and CLI behavior match