docs: Notify users better on incoming module changes, which would require or recommend their intervention

[fiftydinar]

Currently, we only print those notices in build logs, which not all users notice.
And we add the caution notice in extension documentation, which not all users visit frequently.

Perhaps, adding a notification system for this is a great material for adding it in future BlueBuild Workshop?

Maybe we can implement RSS-to-email, to notify the users from the Blog.
However, we would need to visually differ news from feature-update changes & module notices, as they are not the same.

@xynydev What do you think?

[xynydev]

I wrote a longer message here earlier, but forgot to send. Here’s the gist of it:

• A notification system wont be coming any time soon
• We might not have the resources for RSS-to-email, but there are free services that do similar things that users could leverage
• We probably shouldn’t notify about every update but bundle the biggest ones up into one post newsletter-style like Bazzite Buzz
• A lot of changes aren’t breaking changes or urgent, though of course users should be always notified of new module versions like default-flatpaks v2
• Maybe an MOTD module with an optional “BlueBuild MOTD” option would be great, similar to ublue MOTDs it could show latest news like the link to the latest blog post and be styled based on if it has anything actionable for custom image maintainers..?