[MODEUSHARV-93] Extend TenantAPI to restore/remove Quartz scheduled job on tenant enable/disable

[alb3rtino]

https://folio-org.atlassian.net/browse/MODEUSHARV-93

Purpose

Currently, if a periodic harvesting job is scheduled for a tenant and the module is subsequently disabled, the job continues to execute. Conversely, when the module is enabled for a tenant that already has a periodic configuration, the configuration is not picked up and no job is scheduled. This change ensures the Quartz scheduled job is kept in sync with module enablement state.

Approach

• Add TenantAPIImpl extending TenantAPI that removes the scheduled job on tenant disable and restores it from persisted PeriodicConfig on tenant enable/upgrade via loadData.
• Reorder operations in ErmUsageHarvesterPeriodicAPI so that SchedulingUtil.createOrUpdateJob/deleteJob execute before the HTTP response is sent, ensuring the scheduler state is consistent when the client receives the response.
• Add integration tests covering enable, disable, re-enable, upgrade, and a no-config scenarios.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
90.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud