Expose Quartz JobDataMap to persist data between runs when using @Scheduled

[famod]

Description

Quartz provides the so called JobDataMap which you can add mappings to that are persisted so that the next execution can read the previously persisted data. It is available via JobExecutionContext, but that context is not exposed when using @Scheduled (non-programmatic, annotation-driven approach).
Furthermore, the InvokerJob that is registered when using @Scheduled is neither a StatefulJob nor is it annotated with @PersistJobDataAfterExecution, so data won't be persisted.

The goal is to extend quarkus-quartz to opt into persitence and expose the context/map, with the annotation-driven approach.

Implementation ideas

Some ideas were discussed in #25987.

[quarkus-bot]

/cc @machi1990, @mkouba

[famod]

One gotcha (or thing to adjust) is that triggering a job in dev ui creates a DevModeScheduledExecution, not a QuartzScheduledExecution.

[mkouba]

For the record - you should be able to fall back to the Quartz API, annotate the job class with @PersistJobDataAfterExecution and @DisallowConcurrentExecution and schedule the job programmatically.