Add the ability to emit platform wide notifications

[cstns]

Description

Added an admin API that can send platform wide notifications to users that fall into the provided roles.
Added a User model query that retrieves users based on provided roles.

Related Issue(s)

closes #4554

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• Includes a DB migration? -> add the area:migration label

[codecov]

Codecov Report

Attention: Patch coverage is 17.39130% with 19 lines in your changes missing coverage. Please review.

Project coverage is 78.49%. Comparing base (49321fc) to head (a5c9e04).
Report is 47 commits behind head on main.

Files with missing lines	Patch %	Lines
forge/routes/api/admin.js	16.66%	15 Missing ⚠️
forge/db/models/User.js	20.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4637      +/-   ##
==========================================
- Coverage   78.53%   78.49%   -0.04%     
==========================================
  Files         303      304       +1     
  Lines       14398    14493      +95     
  Branches     3285     3308      +23     
==========================================
+ Hits        11307    11377      +70     
- Misses       3091     3116      +25     

Flag	Coverage Δ
backend	78.49% <17.39%> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[knolleary]

Overall, looks good.

One pending question about the 'external url' option - more the ability to provide non-external urls. Not sure how self-hosted admins would know what to do with that.

If there isn't a specific need or example where it will be needed, can I suggest we hide for now to avoid confusion?

[knolleary]

Not sure how this is meant to be used for non-external links. It requires quite a deep knowledge of the UI - something self-hosted users won't have. Is there a specific use-case that requires this capability?

[cstns]

It was mainly for us to know how to properly format the internal url's. I agree there's no use on having it for self-hosted customers. Would leaving the external url as default and hiding the placeholder for the internal routes suffice?

[knolleary]

The default should be external URL, and I don't think we should have the option for it to be anything else. If we wanted to add support for routing internally, then we can sniff the value to decide if its a url or an object - no need to store that otherwise.

[cstns]

I removed the external url selector, forcing all urls to be external

[cstns]

The only task left is inserting data into the notifications table. I’ve added a basic implementation that loops through and inserts notifications into the database based on the roles query.

However, this approach could become problematic if there are many users or results, as it might cause a table lock on the notifications table and lead to other issues.

Should we stick with this for now?

[knolleary]

However, this approach could become problematic if there are many users or results, as it might cause a table lock on the notifications table and lead to other issues.

Should we stick with this for now?

I had a quick look at this part this morning. Had a couple thoughts, but need to poke at it a bit more once other unrelated tasks are complete. Will review tomorrow.