fix: Map 'stable' update channel to 'latest' to resolve HTTP 403

[deshartman]

Summary

• Fixes HTTP 403 error when running twilio update without arguments
• Maps the "stable" channel to "latest" in S3 bucket paths by overriding the S3 templates in package.json
• No infrastructure or workflow changes required

Problem

When running twilio update, users encounter:

Error: HTTP 403: Invalid channel stable

Root Cause: The oclif framework defaults to the "stable" channel, which expects manifest files at the S3 bucket root (e.g., https://twilio-cli-prod.s3.amazonaws.com/twilio-darwin-arm64-buildmanifest). However, these files are either missing or inaccessible at that location.

Solution

This PR adds S3 template overrides in package.json to redirect "stable" channel requests to "latest" channel paths (under channels/latest/ in the S3 bucket). This approach:

• Requires only a code change in package.json
• No S3 infrastructure changes needed
• No workflow modifications required
• "latest" is semantically appropriate for production updates
• Minimal risk - if "latest" doesn't exist, error messages will be clear

Changes

• Updated package.json oclif.update.s3.templates configuration
• Overridden S3 path templates to map "stable" → "latest"
• Other channels (rc, draft) remain unchanged

Test Plan

• All existing tests pass (208 passing)
• Verify twilio update works without 403 error after release
• Verify twilio update --available shows available versions
• Test different channels: twilio update rc, twilio update draft

🤖 Generated with Claude Code