Database support

[FoxxMD]

This PR migrates the entire CM application to use a database for persistence in most contexts, rather than generic cache. There are a myriad of improvements and new features that come along with this refactor. The highlight are below:

Database Features

• Using typeorm for the DAL
  • CM will support these databases: sql.js, sqlite (better-sqlite3), MySQL/MariaDB, and Postgres
  • Avoids driver/binary dependencies by defaulting to sql.js
  • Docker image defaults to sqlite for better performance
  • Both sqlite variants will fallback to memory if database file cannot be read/write
• Actioned Event are stored with all components having tight relations to enable querying arbitrary views of all events
  • Actioned Event UI provides searching by
  • permalink -- optionally, related actitivies IE find all actioned comments by actioned submission or vice versa
  • author
  • All entities stored with timestamps to enable building timing profiles
• Client/Web data (sessions, invites) persisted to DB instead of cache by default
• Delayed Activities (delay via polling, dispatch actions) persisted to DB
• Manager last state persists across restarts via storage in DB
• Statistics
  • All-time stats previously stored in cache are migrated to database on DB init
  • user-configurable frequency stats
• Database migrations are interactive via UI
  • Automatic backup possible if using sqljs/sqlite
  • Separate migrations for client/server architecture

Other Improvements

• Filters
  • Can now be named and re-used the same way rules/actions are
  • Data shape normalized
  • itemsIs has include/exclude/excludeCondition logic implemented, same as authorIs
  • authorIs data shape has a simplified use-case -- defining as an array of AuthorCriteria will assume include the same way itemIs works
• UI
  • Actioned Events now displays Rule Set shape in rule summary
  • Actioned Events display item/author filter name in filter result
  • Actioned Events display source of event IE from which polling source, dispatch action, or user
• Docker
  • Refactored to use linuxserver.io base
  • Improved file permission handling by using a non-root default user and enabling specifying uid:guid via environmental variables PUID PGID
• Config
  • Add DATA_DIR env to specify a folder to find all config/db/log related files in -- simplifies required ENVs for startup
  • Simplified use case for cache/db in client configuration by using top-level cache/db if none specified
  • Specify which to use for session/invite with a storage string key (database or cache)

TODO Before Merge

• [x] Fix and verify manager last state persisted correctly and CM respects last state on init (added in 6d208b3)
• [x] Implement user-configurable frequency stats and default to daily (added in fd173b6)
• [x] Implement config component to specify if events should be stored to database (added in 0a13061)
  • Maybe integrate into postTrigger/postFail?
  • Allow options (many?): none, db, influx (not implemented)
  • top-down override (operator -> subreddit -> run -> check) and/or bottom-up composition (rule/action triggered)
• [x] Implement database event retention policy (added in 24e9295)
  • [x] Policy
  • To specify either 1) the maximum number of events or 2) the maximum age of events to store per subreddit
  • Configurable at operator, bot, subreddit override, or subreddit level
  • [x] Implement scheduler to enforce policy
• [ ] Document all the things
  • [ ] database config and usage
  • [ ] refactor and improve filter docs (with examples)
  • [ ] docker usage and file permission guidance