V16: Retry requests after timeout

[iOvergaard]

Description

This pull request introduces several enhancements and fixes across multiple files, focusing on debugging improvements, dependency updates, and authorization handling. The changes aim to streamline workflows, improve user experience during authentication, and ensure compatibility with updated dependencies.

How to test / Video

2025-06-06.at.14.25.00.-.Emerald.Quail.mp4

(Note: The last example in the video where I had to click twice to show the screen has been fixed by replacing throttleTime with auditTime to wait a bit before firing the timeout signal)

Changes

Debugging Enhancements:

• .vscode/launch.json: Added a postDebugTask to terminate the Umbraco.Web.UI process automatically after debugging sessions. [1] [2]
• .vscode/tasks.json: Introduced a new task, kill-umbraco-web-ui, to terminate the Umbraco.Web.UI process across different operating systems.

Dependency Updates:

• src/Umbraco.Web.UI.Client/src/packages/core/package.json: Updated versions of @hey-api/client-fetch and @hey-api/openapi-ts dependencies.

Authorization Handling Improvements:

• src/Umbraco.Web.UI.Client/src/apps/backoffice/backoffice.element.ts: Refactored the authorization flow to ensure private extensions are registered only after successful authorization. (Mentioned in v15/v16: Race conditions after UMB_AUTH_CONTEXT -> isAuthorized and private manifests #19485 but does not fully fix that issue)
• src/Umbraco.Web.UI.Client/src/packages/core/auth/auth.context.ts: Improved observables for authorization and timeout signals by adding throttling and distinct change detection. [1] [2] [3]

API Enhancements:

• src/Umbraco.Web.UI.Client/src/packages/core/resources/api-interceptor.controller.ts: Enhanced interceptors for handling 401 and 403 responses, including retry logic for GET requests and better error notifications for non-idempotent requests. Introduced mechanisms to queue and retry unauthorized requests after re-authentication. [1] [2] [3]
• All errors will now come in an UmbProblemDetails shape. This allows the client to show more comprehensive error messages rather than just the default "An error occurred".
• The mapToUmbError has been improved so that the UmbError base type is no longer used and only UmbApiError and UmbCancelError are. This allows people using tryExecute to expect that it is an api error happening.
• Moved all error notifications to the UmbTryExecuteController so we don't have part of it happening in an interceptor (500 errors) and the rest there. We now put all of it in tryExecute, which also allows you to ignore all error notifications.

These changes collectively enhance the development workflow, improve debugging and authorization handling, and ensure compatibility with updated dependencies.