Consider using Sentry with scriptworkers

We use Sentry for most of our long running web apps, mainly for its ability to track tracebacks. We ought to consider doing the same for scriptworkers. According to https://docs.sentry.io/platforms/python/#configure, it's very simple, just:

mport sentry_sdk

sentry_sdk.init(
    dsn="

https://8d0b074c42d54a60afd0f6196259bac6@o1069899.ingest.sentry.io/6262508",

    # Set traces_sample_rate to 1.0 to capture 100%
    # of transactions for performance monitoring.
    # We recommend adjusting this value in production.
    traces_sample_rate=1.0,
)

This would allow us to get tracebacks more easily than it is through the GCP console, maybe allow self serving of alerts, notifications, etc.

Review the scriptworker startup path, current traceback handling through the GCP console, and the linked Sentry Python configuration documentation. Confirm which scriptworkers should report errors and what alerting or notification behavior is expected; done means the agreed workers report useful tracebacks without disrupting their existing execution.