LWLP-1106: Improve notifications 403 error message

[ochosi]

Summary

When a 403 (Forbidden) is returned from the notification subscriptions or user preferences query, the global query error handler now shows a clear permissions message instead of the raw HTTP status, directing the user to contact their org admin for access.

TODO: Get the names of the exact permissions that are missing so users can reach out to their org admins in a more actionable/meaningful way.

Testing steps

n/a

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.72%. Comparing base (7421c6e) to head (de6dcf2).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1223      +/-   ##
==========================================
- Coverage   63.90%   63.72%   -0.19%     
==========================================
  Files         149      149              
  Lines        5511     5511              
  Branches     1077     1077              
==========================================
- Hits         3522     3512      -10     
- Misses       1688     1697       +9     
- Partials      301      302       +1     

Flag	Coverage Δ
e2e	63.72% <ø> (-0.19%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes

🚀 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.

[ochosi]

This will be fixed in the notifications service so we don't expect any specific 403 errors.