Read-only users are logged out when they bookmark, rename or delete an execution #9324

What happened?

A user with read-only access to a workflow can click bookmark, rename and delete in Execution History. The backend refuses these with a 401:

// amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowExecutionsResource.scala:92
throw new WebApplicationException(Response.Status.UNAUTHORIZED)

UnauthorizedHttpInterceptor treats any 401 on an authenticated request as an expired session, so the user is logged out and sent to the login page with "Your session has expired. Please log in again." Their session is still valid; they just lack permission.

This should be a 403, like the "No sufficient access privilege." refusals in WorkflowResource.

How to reproduce?

1. With GUI_WORKFLOW_WORKSPACE_WORKFLOW_EXECUTIONS_TRACKING_ENABLED=true, run a workflow and share it with a second user as read-only.
2. As the second user, open Execution History for that workflow.
3. Click the star on an execution.

Version/Branch

1.3.0-incubating-SNAPSHOT (main)