[wedamija]

Part of a series adding automatic Crons monitoring for the most-used job schedulers in each SDK. Check-ins for a monitor that doesn't exist yet are dropped, so today each monitor has to be created by hand with its schedule copied from the code. Sending the job's schedule as the monitor config lets Sentry create the monitor and keep it in sync.

This adds SentryQuartzOptions.MonitorAllJobs, which monitors every scheduled job without adding [SentryMonitorSlug] to each job class, and ExcludedJobs to skip some by name, full key or regex. The monitor slug comes from the job key. Jobs with [SentryMonitorSlug] keep their own settings. Off by default.

services.AddQuartz(quartz =>
{
    quartz.AddSentry(options =>
    {
        options.MonitorAllJobs = true;
        options.ExcludedJobs.Add("reports.Adhoc");
        options.ExcludedJobs.Add(new Regex(@"^maintenance\."));
    });
});

Only runs fired by a trigger whose schedule Sentry can represent are monitored, so one-off runs like TriggerJob, triggers with a calendar and cron expressions Sentry can't express are skipped, as in sentry-python. Jobs with several triggers on different schedules, or that share a monitor slug with a job on a different schedule, are skipped too, since their monitor config can't be built.

Stacked on #5505, through the danf/quartz-5505-rebased branch since that PR's head is on a fork.

[linear-code]

NET-180

NET-483

[jamescrosswell]

LGTM - thanks @wedamija ❤️