[Sentry UI] Consistently Confirm Destructive Actions

[souredoutlook]

Problem Statement

It's currently very easy to destroy key org and project settings and auth tokens in Sentry.

For example, when copying an Auth Token from https://org-slug.sentry.io/settings/account/api/auth-tokens/, it is very easy to click Remove instead of Copy:

This action requires no confirmation step and may result in broken production systems.

For internal integration auth tokens (https://org-slug.sentry.io/settings/developer-settings//), the view is arranged in such a way that accidentally revoking the token instead of copying it is much more difficult:

Some other areas where destructive actions can be taken without a confirmation step: Organization Security and Privacy Settings (https://org-slug.sentry.io/settings/security-and-privacy/):

• Global Sensitive Fields
• Global Safe Fields

Project Settings (https://org-slug.sentry.io/settings/projects//):

• Email Subject Prefix
• Allowed Domains
• Security Token
• Security Token Header
• Removing a Project Team (https://org-slug.sentry.io/settings/projects//teams/)
• Alert Settings - Email Titles, Digests Frequencies
• Most other project settings including inbound filters and project level safe and sensitive fields

Solution Brainstorm

In the case of user auth tokens, see the feedback from this tweet:

A little product improvement address here: Can you separate the copy and remove button a little wider? I just delete a token ran on pre-production env. @getsentry it will be very helpful. Thank you…

Other product areas such as text fields that update on change would likely benefit from a confirmation step similar to the one shown here when trying to change a project slug:

[getsantry[bot]]

Assigning to @getsentry/support for routing, due by Tuesday, March 14th at 12:39 (yyz). ⏲️

[getsantry[bot]]

Routing to @getsentry/core-ui for triage, due by Wednesday, March 15th at 9:39 am (sfo). ⏲️