SAML SSO setup fails silently with no error/warning message

### Environment

SaaS ([https://sentry.io/]())

### Steps to Reproduce

1. Go to Organisation settings -> Auth
2. Configure SSO via SAML using any of the options in the list.
3. Have one misconfiguration during the process.

### Expected Result

When completing the setup, Sentry UI should show a message showing that the setup failed with the reason why it happened.

This message allows the user to identify the root cause, fix the issue and successfully configure SSO.

### Actual Result

Sentry redirects user to the Auth page again, SSO is not configured and no error/warning message is shown.

### Product Area

Settings - Auth

### Link

*No response*

### DSN

*No response*

### Version

*No response*

We want to define a set of [lightweight metrics]() that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.

Examples**:**

* Node.js runtime metrics (e.g., event loop delay, heap usage)
* Prisma-related metrics in Next.js
* Mobile CPU / memory usage to help surface potential ANRs or app hangs

---

**Candidate Metrics (add more below)**

* …

*(please also add ideas, questions or examples in comments)*

Start at Organisation settings → Auth and reproduce a SAML setup with a deliberate misconfiguration. Trace the setup failure and redirect path to find where the reason is lost; done means the Sentry UI displays a useful failure message and the user can identify what to fix.

Written by the indexing model from the issue text.