Update behaviour when license expires

[Steve-Mcl]

Description

Based on notes in #1739

• (Admin Only) Show banner when warn period is started (hard coded to 30 days - see TO DECIDE below)
• (All Users) Show banner when grace period is started
• (All Users) Show banner when grace period is ended
• Send Email to all platform admins
  • upon hitting warning period
  • upon grace period
  • upon end of grace period
• As it stands, projects will NOT be suspended when grace ends. (see TO DECIDE below)

TO DECIDE

• Currently, a hard coded app.config option named license_warn_period is set for 30 days
  • consider making a user config option?
  • NICK: No ✅
• Currently, a hard coded app.config option named license_grace_period is set for 30 days
  • Should the license itself specify this? (billable grace period?)
  • NICK: No ✅
• Currently, a hard coded app.config option named license_expiry_stops_all is set to false. Essentially meaning projects will NOT be stopped on expiry by default / as it stands.
  • Do we want to enable this?
  • Should the license itself specify this? (billable feature?)
  • NICK: No - latest proposal is to leave projects running ✅
• What to do with devices?
  • In the issue I think i wrote "yuk" to the proposal (sorry 😉) - i personally think we either leave them alone or update the device agent to accept a kill switch.
  • NICK: No longer relevant since latest proposal is to leave projects running ✅

Screenshots of UI changes

Click to reveal

License Warning (30 days or less to expiry)

License Grace (less than 30 days after expiry)

License and grace expired

Changes

• Add grace and warning constants
• Add license.status meta data to vuex settings
• add email templates
• add housekeeper to check license state
• reroute admin to license page if expired
• add banner to pages (user/license state dependant)
• add mockdate to devdeps for testing license expiry
• add tests for license expiry

Related Issue(s)

#1739

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• [-] Documentation has been updated *** (separate task in Review documentation and update the 'big picture' around licensing #1745) ***
  • Upgrade instructions
  • Configuration details
  • Concepts
• [-] Changes flowforge.yml?
  • Issue/PR raised on flowforge/helm to update ConfigMap Template
  • Issue/PR raised on flowforge/CloudProject to update values for Staging/Production

Labels

• [-] Backport needed? -> add the backport label
• [-] Includes a DB migration? -> add the area:migration label

[knolleary]

consider making a user config option?
No

Should the license itself specify this? (billable grace period?)
No

license_expiry_stops_all is set to false.
Do we want to enable this?
Should the license itself specify this? (billable feature?)

This is the discussion in #1739 which is where any other proposals should be discussed. I don't want one set of things agreed in the issue and then a different set of things implemented in the PR.

In the issue I think i wrote "yuk" to the proposal (sorry 😉) -

The proposal was based on what we could do today. It made it clear there were problems with that approach.
However, the proposal also changed to keep things running after the grace period. In which case we don't need to do anything with devices.

[knolleary]

The implementation feels like it is caught between the two proposals of #1744 - whether to suspend projects at end of the post-expiry grace period.

The current proposal is not to suspend projects. In which case a post-expiry grace period doesn't serve much purpose and should be removed from this PR.

But until we sign-off #1739 it's hard to sign-off an implementation.

[knolleary]

Sorry, got my issues mixed up - have mentioned #1744 a lot when I should have said #1739 - have edited the comments to correct it.

[knolleary]

Aside from one comment, all looks okay.

[Steve-Mcl]

Committed suggestion to remove leftover debugging code/comment.