Is your feature request related to a problem? Please describe.
When a hijack alert has not seen any updates for a user-defined time window (e.g., 24 hours), it should
be considered still active (ongoing), but also have an extra tag called "dormant". There is no need to change existing DB constraints for this, except add a constraint that active and dormant flags cannot be set as (false, true), but need to be within [(true, true), (true, false), (false, false)].
Describe the solution you'd like
An extra "dormant" field in the db (defaulting to false), that is automatically set if the alert has not seen sth for at least X hours (defined by the user in .env). This can be dealt with with a cron job in postgres, that does sth like this in pseudocode:
SELECT all hijack alerts with time_last < NOW - interval, which have the active flag set to True and the dormant flag to False, and set the dormant flag to True.
This will also require support from the frontend, since a new tag is added. Note that whenever the active flag is set to false, the dormant flag should also change too (see proposed constraints).
Whenever the time_last is updated (see database.py actions), the dormant flag should be directly set to False again!
DB migration will also be required to add the new field in the hijacks table.
This change will require changes in the wiki too.
Describe alternatives you've considered
N/A
Additional context
N/A