Add task scheduler to backend services (cron jobs)

[spwoodcock]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

• Auto unlock locked tasks after 3 days #1984
• Automatically unlock tasks that have been locked for more than 3 days #1603
• GDPR Compliance: warn users their account will be deleted after two years inactivity #1999
• Allow super admin or project creator to unlock task or revert to ready for mapping #2181
• Warn users and delete user accounts after period of inactivity  #2088

Describe this PR

• Using cron in a container without root is actually really difficult. We need root to run the cron daemon.
• Instead I added supercronic, a go binary specifically built to replace cron in containers.
• This runs as part of the local development compose stack.
• As we don't build a specific container for this, it's much more flexible. We can replace the compose service with a Kubernetes CronJob as needed.
• The python scripts to run are under /src/backend/scheduled/xxx.py
• TODO:
  • Update the code in the linked PRs so the logic happens entirely in xxx_crud.py modules. The xxx_routes.py code should simply call the logic. This way we can replicate this in the /src/backend/scheduled/xxx.py too.
    • Unlock tasks / features
    • Delete old user accounts
    • Trigger ODK photo upload?
  • Remove any requirement on the request: Request var from logic, as we can't use this on a schedule (instead we need to use a service account OSM token to send emails).
  • Test thoroughly.
  • Add compose services to remaining compose files + deploy.

Alternative Approaches Considered

• I tried many ways of using cron. All pretty impossible without root, if we want to receive any kind of logging.
• I also considered an approach using a simple sleep command: https://gist.github.com/mowings/a32fbf4dd46d9fb9661822056ceda91c, but it's very difficult to work the syntax as part of the compose command: section.

Review Guide

• For testing, replace the cron schedule in compose.yaml with * * * * * to run every minute.

Checklist before requesting a review

• 📖 Read the FMTM Contributing Guide: https://github.com/hotosm/fmtm/blob/main/CONTRIBUTING.md
• 📖 Read the HOT Code of Conduct: https://docs.hotosm.org/code-of-conduct
• 👷‍♀️ Create small PRs. In most cases, this will be possible.
• ✅ Provide tests for your changes.
• 📝 Use descriptive commit messages.
• 📗 Update any related documentation and include any relevant screenshots.

[optional] What gif best describes this PR or how it makes you feel?

[spwoodcock]

I won't work any more on this for now - moving onto MdP work.

Everything is in place to continue the work for unlocking inactive users and tasks @Anuj-Gupta4 🙏

Although I would say this is one of the lower priority items on our roadmap, to be addressed by anyone when there is some free time.

[Anuj-Gupta4]

This looks great! I'll make a few minor adjustments to refine it for now and come back to it later.