403 errors show an unfriendly "Network Response 403" message

Description

When the database or proxy returns a 403 Forbidden, the user sees the generic Network Response 403 title with whatever raw message the server returns, which is often an opaque JSON blob or empty. There is no dedicated branch in createDisplayError for 403, so it falls through to the catch-all NetworkError path.

A 403 can be caused by several things (credentials, permissions, proxy configuration), so the message should stay generic and point the user at what they can reasonably check.

Environment

• All environments, browser-based

Steps to Reproduce

1. Connect to a database or proxy that will reject requests with 403
2. Trigger any request (e.g. schema sync)

Expected Behavior

A friendly, generic message such as:

Access denied The server refused this request. Check that your connection credentials and permissions are correct, then try again.

Actual Behavior

Title says "Network Response 403" and the message is either the raw server response or the generic "An error occurred. Please try again."

---

[!IMPORTANT] If you are interested in working on this issue, please leave a comment.

[!TIP] Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.