Release 33.10

What's new

• Added cronitor team list, cronitor team invite, cronitor team role, and cronitor team remove. A member's id is their email address.
• Added cronitor apikey to list, get, create, update, and delete API keys. The table masks each key, and --format json prints it in full.
• cronitor auth login --admin creates an account-access key. cronitor team and cronitor apikey then act with your current role.
• Read-only users can't use cronitor apikey, even with --admin.
• Don't use --admin on shared servers or CI hosts.
• Removing a team member deletes only keys created with cronitor auth login --admin. Keys from a plain cronitor auth login belong to the organization and keep working. Outside cronitor team and cronitor apikey, demoting someone does not reduce what their existing keys can already do, so delete their keys and have them log in again.
• team remove and apikey delete ask for confirmation, and need --yes when stdin isn't a terminal.
• New aliases: teams, apikeys, keys.
• --format accepts json or table (and yaml only for monitor), and -f, --file applies to monitor create/update and integration create.
• Fixed help and README examples for issue, site, maintenance and statuspage so they use real flags and valid API payloads (#69).
• cronitor team, cronitor apikey, and auth login --admin need Cronitor's matching server update. Until it is live, --admin login warns that account access was not granted.