Describe the bug

Not sure if this is a bug or intended. We're setting a cron trigger with a start and end date where both are already expired (we'll fix this anyway but just want to check the desired internal behaviour). E.g.

With start date = 01-01-1970
End date = 01-01-2023
Cron = "0 30 14 ? * MON,TUE,WED,THU,FRI *"

                return builder
                    .StartAt(startDate)
                    .EndAt(endDate)
                    .WithCronSchedule(cron, m => m.WithMisfireHandlingInstructionFireAndProceed());

Expected behaviour is the trigger never fires, but the actual behaviour is it schedules for 01/01/1970 14:30:00 +00:00, which then runs immediately due to misfire handling I think

Version used

3.8.1

To Reproduce

The steps above.

Expected behavior

The trigger never fires.