refactor: add typed getHttpErrorStatus helper and PlatformError type

[dcoa]

Summary

Consolidates the scattered request error's HTTP status into one typed helper, removing the as any / @ts-ignore / lie-to-the-compiler patterns that were duplicated across the module.

What and why

• getHttpErrorStatus(error: unknown): number | undefined, which safely reads the status the auth client attaches to thrown errors.
• PlatformError interface that return the AxiosError shape.

Small clean ups

• ToastManagerContext clears pending toast-removal timers on unmount and wraps showToast/discardToast in useCallback (fixes a setState-after-unmount risk and a stale-closure in the context value).
• audit-user typed the previously-implicit-any runRevokeRole param ({ data: RevokeUserRolesRequest }).

AI use acknowledgement

Supported by Claude Code

[openedx-webhooks]

Thanks for the pull request, @dcoa!

This repository is currently maintained by @openedx/committers-frontend.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.39%. Comparing base (e3d90d8) to head (543fef9).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #171      +/-   ##
==========================================
- Coverage   97.44%   97.39%   -0.05%     
==========================================
  Files          66       66              
  Lines        1525     1535      +10     
  Branches      386      385       -1     
==========================================
+ Hits         1486     1495       +9     
- Misses         39       40       +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.