Deleting a card in a read only board fails but is shown as succeeded

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Describe the bug
Deleting a card in a read only board fails but is shown as succeeded.

To Reproduce
Steps to reproduce the behavior:

1. Create a new board with user A
2. Create a new stack with user A
3. Creae a card with in stack wih user A
4. Share the board with user B read only
5. Delete the card with user B

The request fails with HTTP 403 and a success message is being produced and presented to the user B.

Expected behavior
The request fails with HTTP 403 and an error message is being produced and presented to the user B.

Screenshots

Client details:

• OS: N/A
• Browser Firefox
• Version 142.0.1
• Device: desktop

No errors have been found.

if needed on request

if needed on request

Logs

Nextcloud log (data/nextcloud.log)

No relevant entries

Browser log

See screenshot above.

Uncaught (in promise) 
Object { message: "Request failed with status code 403", name: "AxiosError", code: "ERR_BAD_REQUEST", config: {…}, request: XMLHttpRequest, response: {…}, status: 403, stack: "", … }
vuex.esm.js:542:7
    dispatch vuex.esm.js:542
    (Async: promise callback)
    dispatch vuex.esm.js:519
    dispatch vuex.esm.js:518
    dispatch vuex.esm.js:406
    deleteCard CardMenuEntries.vue:151
    click CardMenuEntries.vue:1
    VueJS 4
    onClick actionText-fFcUPi2g.mjs:77
    handleClick NcActionButton-CuVNJJtW.mjs:143
    VueJS 33

Start at the deleteCard entry point in CardMenuEntries.vue around line 151 and inspect how the failed Axios request is handled, using the browser log as context. Reproduce the read-only board scenario and verify that the HTTP 403 displays an error message instead of a success message.