Ensure purgeTablesBean uses the correct datasource during clean operation

[jpdev01]

Previously, when running the clean operation, the purgeTablesBean incorrectly targeted the main application dataSource instead of the jdbcStoreDataSource specified in the Quartz properties.

This PR updates the configuration of purgeTablesBean to dynamically resolve the dataSource based on the org.quartz.jdbcStoreDataSource property. If this property is not defined, it will fallback to the default dataSource.

• Changes:

Updated the purgeTablesBean to use properties['org.quartz.jdbcStoreDataSource'] ?: 'dataSource' for resolving the dataSource.
Ensures the clean operation now targets the correct database when jdbcStoreDataSource is provided.

• Impact:

This fix prevents unintended operations on the main application database when a custom jdbcStoreDataSource is configured.

• Testing:

Verified that clean operations now correctly use the jdbcStoreDataSource when specified.
Confirmed fallback to the main dataSource when org.quartz.jdbcStoreDataSource is not configured.

[CLAassistant]

All committers have signed the CLA.

[jpdev01]

I created the PR for version 2.0, but this issue is also present in the current version. I have opened another PR for the current version as well.

#135

[jamesfredley]

@jpdev01 once this one gets reviewed and merged, it will get merged up to 3.0.x and 4.0.x. Do you need it on the 2.0.x branch which supports Grails 3-5? Either ways is fine, just wanted to confirm.

@arjangch can you review this change?

[jpdev01]

@jpdev01 once this one gets reviewed and merged, it will get merged up to 3.0.x and 4.0.x. Do you need it on the 2.0.x branch which supports Grails 3-5? Either ways is fine, just wanted to confirm.

@arjangch can you review this change?

Currently, we are using version 2.0.13 of Quartz in our production application. Ideally, I would need this solution for the 2.0.x version. Is that possible?

[jamesfredley]

@jpdev01 yes, we will do it for 2.0.x, 3.0.x and 4.0.x.

[jamesfredley]

#137 - merging up to 3.0.x

[jamesfredley]

#138 merging up to 4.0.x

[jamesfredley]

@jpdev01 @Kpotz @amondel2 @arjangch Are we ready for 2.0.14 and 3.0.1 releases which include this change?

2.0.14-SNAPSHOT, 3.0.1-SNAPSHOT and 4.0.0-SNAPSHOT have it.