🚧 Feature/sentry.quartz (Quartz v4 Alpha version)

[michaelmairegger]

This PR implements and showcases Quartz.Net integration for Sentry

Note: Quartz.Net v4 is still alpha, therefore we should wait until v4 is finally released.

fixes #4601

[michaelmairegger]

@jamescrosswell I will continue watching Quartz.Net alpha releases and adopt it until final bits of 4.0 will be released.
I will notify you when ready.

[jamescrosswell]

@jamescrosswell I will continue watching Quartz.Net alpha releases and adopt it until final bits of 4.0 will be released. I will notify you when ready.

Fantastic, thank you @michaelmairegger !

Maybe we mark the PR as draft until then? That let's me know it doesn't yet need my attention (you can always tag me directly if you want my input on something before v4 is released).

[sentry]

Bug: The code incorrectly slices a normalized cron expression using normalized[1..6], which omits the 'minutes' field and passes a malformed cron string to Sentry, causing monitor creation to fail.
_{Severity: HIGH}

Suggested Fix

Change the array slice from normalized[1..6] to normalized[0..5]. This will correctly extract the first five fields (minute, hour, day, month, weekday) to form a valid 5-field Unix cron expression as expected by Sentry.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: src/Sentry.Quartz/SentryCronJobMiddleware.cs#L104-L108

Potential issue: In the `UpsertCronMonitor` method, the code attempts to convert a
Quartz cron expression to a 5-field Unix format for Sentry. It correctly parses the
expression, resulting in a 6-field string (including seconds). However, it then uses an
incorrect array slice `normalized[1..6]` to extract the fields. This slice omits the
'minutes' field (at index 0) and creates a malformed 5-field string. This malformed
string is passed to `SentryMonitorOptions.Interval()`, which will cause a validation
failure and an `ArgumentException`. The exception is caught and logged, but it results
in the cron monitor failing to be created, silently breaking the feature.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 59fdcd8. Configure here.}