fix: too_many_open_prs() fails without SSO access

[elijaholmos]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew typecheck with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

Resolves #18610 by implementing the suggested solution:

Ignoring any SSO (i.e. extensions contains saml_failure) errors for that specific API call only. SAML errors for other API calls are likely genuine and should continue to error.

extensions doesn't appear to be present on this response when an SSO error is thrown. Instead, a check is performed to determine if the error message contains "SAML"; if so, the error is disregarded. I understand "SAML" may be too wide of a filter- please suggest a more narrow alternative if that is the case.

[MikeMcQuaid]

Thanks @elijaholmos! One thought on improving message checked.

[MikeMcQuaid]

Thanks so much for your first contribution! Without people like you submitting PRs we couldn't run this project. You rock, @elijaholmos!