Implement `wasp news`

[sodic]

We want a channel to tell users about important updates in wasp (e.g., new versions, security updates). We want to do this with a new CLI command: wasp news.

Here's how our prototype currently works:

• Calling wasp news explicitly prints out all news of all levels.
• wasp start commands prints all news once per day until the user runs explicitly runs wasp news to acknowledge them.

What's left to decide:

• How many priorities/levels do we want and what's their semantics (i.e., when to show and repeat what).
• Decide when to show news (just wasp start, all commands, etc.).
• Decide how we want to mark news as "read:"
  • When the user runs wasp news as we currently do.
  • Interactively - we block and wait until they acknowledge them. This might be annoying in the CI.
• Decide whether and how we want to mark unseen news.

What's left to implement:

• Implement the new/changed features we decide to have.
• Polish the code and remove all the hacks.
• Replace the news server with a static file.

[sodic]

Decisions @Martinsos and I made:

• Wasp news have 3 levels: Critical (e.g., security vulnerabilities), Important (e.g., Wasp versions), and Info (not sure yet but maybe launch weeks).
• Users can see all news with the wasp news command.
• Running wasp news marks all shown news as "seen."
• We draw the news from a static json file on our website.
• We show some news during wasp start and we check for new news once per day:
  • Critical news (e.g., security vulenrabilities) block wasp start and ask users for explicit confirmation before the command continues. When the user interactively confirms they've read the news, they are considered "seen" and no longer show up on wasp start. Since we're only showing news on wasp start, this won't cause problems in the CI (plus, we'll add an env var for disabling wasp news).
  • Important news (e.g., new Wasp versions) are shown on wasp start but don't block execution. We fetch and show them once per day until the user explicitly runs wasp news to mark them as seen.
• Info news are only shown when users run wasp news, never on wasp start.

[infomiho]

Important news (e.g., new Wasp versions) are shown on wasp start but don't block execution. We fetch and show them once per day until the user explicitly runs wasp news to mark them as seen.

I think this might be too aggressive, I'd maybe show them up to 3 times or something like that. Or just once.

EDIT: Okay, it's once per day. But still, what if there are 4, 5 important news that the user never cleared. Do news have an expiry date?