feat: add --schema and --data options for email and phone provider commands

[ramya18101]

🔧 Changes

Extends the JSON-input / schema-discovery flag surface (already on actions, roles, users, apis, apps, connections, logs, domains, email templates, universal-login, and acul config) to the email and phone provider commands, so agents and automation get the same whole-payload and schema-discovery interface. All flags reuse the existing shared helpers (internal/cli/schema.go, data_json.go, query_json.go); no new flag machinery was introduced.

The flags

• --schema: prints the OpenAPI request/query schema for the operation and exits (combine with --json/--json-compact for machine-readable output).
• --data: whole-payload JSON for create/update: inline JSON, @file.json, or piped stdin; validated against the OpenAPI schema before the API is called.
• --query/-q: JSON object of query parameters for list commands.

Per command

Command	Added
email provider create	--data + --schema (POST /emails/provider)
email provider update	--data + --schema (PATCH /emails/provider)
phone provider list	--schema + --query (GET /branding/phone/providers)
phone provider create	--data + --schema (POST /branding/phone/providers)
phone provider update	--data + --schema (PATCH /branding/phone/providers/{id})

Notable decisions

• --data is mutually exclusive with every granular input flag via markDataExclusive, matching the other groups.
• With --data, email provider update and phone provider update skip the pre-read and the interactive prompts and send the payload verbatim.
• --schema returns before the provider ID is resolved, so phone provider update --schema needs no ID.

📚 References

• OpenAPI spec: https://auth0.com/docs/oas/management/v2/management-api-oas.json
• feat: add '--schema' and '--data' options for various commands  #1691

🔬 Testing

Manual smoke (against a tenant, non-mutating):

auth0 email provider create --schema                      # POST /emails/provider
auth0 email provider update --schema                      # PATCH /emails/provider
auth0 phone provider list --schema                        # GET /branding/phone/providers
auth0 phone provider create --schema                      # POST /branding/phone/providers
auth0 phone provider update --schema                      # PATCH /branding/phone/providers/{id}
auth0 phone provider list --query '{"disabled":false}' --json

📝 Checklist

• All new/changed/fixed functionality is covered by tests (or N/A)
• I have added documentation for all new/changed functionality (or N/A)

🤖 Generated with Claude Code

[developerkunal]

Thanks for this. The five commands follow the same pattern as the other groups, and build, unit tests, lint and the docs check all pass. I also ran every command live against a dev tenant, and --schema, --query and --data behaved as expected. There are two things to fix before this can merge, and one question. Details are in the inline comments.

[developerkunal]

Question, not blocking. For a custom email provider, creating it with flags works without credentials (the help example does exactly that, and the API accepts it). Creating the same thing with --data is rejected locally with schema validation failed: property "credentials" is missing, because the OpenAPI schema marks credentials as required. Is that gap intended? If not, it may be worth a follow-up so an agent can reproduce the custom example through --data.