[platform, crons-python] deploy non-GAE projects, starting with Crons

[realkosty]

Corresponding empower-config PR: https://github.com/sentry-demos/empower-config/pull/12

Testing

https://demo.sentry.io/crons/?project=4505197623705600&statsPeriod=1h&timeWindow=24h

./deploy.sh --env=production crons-python
env = production
You are about to do a deployment to production, but current code is different from HEAD at
    sentry-demos/application-monitoring AND/OR your production.env is different from production.env in
    sentry-demos/application-monitoring-config:
 bin/validate_env.sh            |  8 ++++----
 bin/validate_project.sh        |  6 +++---
 crons-python/crontab.template  |  1 +
 crons-python/deploy_project.sh | 21 +++++++++++++--------
 crons-python/main.py           | 15 ++++++++++-----
 crons-python/validate_env.list |  5 +++++
 deploy.sh                      | 10 +++++++++-
 ... (4 more lines)
Type 'yes, deploy to production' to continue... yes, deploy to production
|||
||| ./deploy.sh: crons-python
|||
Requirement already satisfied: sentry-sdk==1.23.0 in ./env/lib/python3.10/site-packages (from -r requirements.txt (line 1)) (1.23.0)
Requirement already satisfied: certifi in ./env/lib/python3.10/site-packages (from sentry-sdk==1.23.0->-r requirements.txt (line 1)) (2023.7.22)
Requirement already satisfied: urllib3>=1.26.11 in ./env/lib/python3.10/site-packages (from sentry-sdk==1.23.0->-r requirements.txt (line 1)) (1.26.18)

[notice] A new release of pip is available: 23.0.1 -> 23.3.1
[notice] To update, run: pip install --upgrade pip
Checking ssh connection can be established...
Checking state of current deployment...
Copying code to remote directory...
Code copied.
No need to install requirements, because no changes to requirements.txt, env exists on remote host and is not empty.
EXISTING crontab:

*/5 * * * * /home/kosty/empower-crons-python/run.sh
---
UPDATED crontab:

*/5 * * * * /home/kosty/empower-crons-python/run.sh
---
Done. New code should be picked up when cron job runs next time.