When storing job with replace check update count returned

[t-beckmann]

This is to detect non-durable job suddenly disappearing when concurrently completing. On MariaDB/MySQL the fall-through code path select-update-insert can be taken due to consistent nonblocking read and multi-version concurrency control.

In submitting this contribution, I agree to the current Software AG contributor agreement as referred to here:
https://github.com/quartz-scheduler/contributing/blob/main/CONTRIBUTING.md

Changes

The code change checks the update count returned when storing a job.

Checklist

• tested locally
• updated the docs (not applicable, bug fix only)
• added appropriate test (not applicable, storeJob method covered in tests already)
• signed-off on the above mentioned SoftwareAG contributor agreement via git commit -s on my commits.

Fixes #1085