chore: Fix up handler type

[nalanj]

I kept noticing spots where I was getting eslint errors because of our handlers being async but the handler type expected void and not Promise<void>. This updates the type for handlers and cleans up the resulting type errors.

If you want to see this in action, before switching to this branch check out line 125 in packages/jobs/lib/routes/tasks/putTask.ts. It has an eslint warning because of a misused promise. After this update that eslint warning is gone.

[nalanj]

🍖 You can see down at line 22 that we generally treat it as a promise anyway.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8205899	Triggered	Generic Password	46a49ce	packages/cli/docker/docker-compose.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}