feat(jobber): migrate to temporal

[dargmuesli]

This pull request introduces Temporal (a workflow orchestration system) into both the development and production environments, replacing the previous job scheduling solution (jobber). It removes all jobber-related configuration, secrets, and scripts, and sets up Temporal and its worker services with appropriate monitoring and database access. The documentation is updated to reflect these changes, and Prometheus/Grafana alerting is extended to monitor Temporal workflow failures.

The most important changes are:

Migration from Jobber to Temporal:

• All jobber service definitions, configurations, secrets, and related notification scripts are removed from both development and production environments (src/development/jobber/, src/production/jobber/, and references in compose files).
• New temporal and temporal-worker services are introduced in both development and production, with appropriate configuration for secrets, environment variables, and volumes.

Secrets and Database Integration:

• Secrets for Temporal's database roles are added to Postgres configuration, and sqitch is updated to include these secrets. Temporal worker is configured to use the same S3 bucket and credentials as the previous jobber for backup tasks.

Monitoring and Alerting:

• Prometheus is configured to scrape metrics from the new Temporal service, and a Grafana alert is added to notify about Temporal workflow failures.

Documentation Updates:

• The documentation is updated to remove references to jobber and add instructions and endpoints for accessing Temporal and its UI.

Entrypoint and Service Initialization:

• A custom entrypoint script is added for Temporal in development to handle Docker secrets and environment variables correctly.