Persist begun transactions in db

[LucaBernstein]

Triggers:

• tx open for longer than n hours (checked by cron)
• admin command /admin_persist_all_open yes

Actions:

• All tx currently opened are persisted in db
• user is notified, that currently running tx has been canceled. furthermore: If you want to continue where you left off, please type '/restore 20220124_<some_generated_name_or_details_or_none_if_unique>
• add callback button with restore 2021.....
• remove transaction from currently running

Implementation

• as described above
• test for caching, incl. generated sql, check that it works, also check sql and inject the same (same variable) into a test testing the other direction of restoring.

Bonus

• Do final sync on SIGTERM and SIGKILL: https://gist.github.com/uudashr/3cf820e3ba902d3c6387abc82c815e66

---

• Still use app cache
• If user enters tx input and there is no tx found locally, check db
• For each tx input (async) write cache state to db (and locally)
• Delete committed tx from db

[LucaBernstein]

Dockerfile: depend bot service on db to help Docker in ordering app restarts

[LucaBernstein]

reduce cache time, store and retrieve from db instead