Team command parameter consistency: --email vs --user-id

Issue

The team commands currently use inconsistent parameter names for identifying users:

• team invite --email <string> - Uses email for inviting
• team update --user-id <string> - Uses user-id (UUID) for updating
• team remove --email <string> - Uses email for removing

Questions

1. Should we standardize on one approach?

   • Option A: Always use --email for user identification
   • Option B: Always use --user-id for user identification
   • Option C: Keep current behavior (different commands use different identifiers based on what's most natural)

2. If we standardize, which identifier is preferred?

   • Email is more user-friendly and human-readable
   • User ID (UUID) is more consistent with instance/VPC commands that use numeric IDs

Context

This was discovered during a CLI parameter consistency audit. All instance and VPC commands now consistently use --id flags instead of positional arguments.

Review the team invite, update, and remove command entry points and compare their current user-identification parameters with the instance and VPC commands. Resolve whether email or user ID should be standardized, then define the expected consistent CLI behavior and verify each team command follows it.