Allow to configure Quartz's "overwriteExistingJobs" property

See gh-13582

spring-boot-project/spring-boot-docs/src/main/asciidoc/appendix-application-properties.adoc

@@ -146,6 +146,7 @@ content into your application. Rather, pick only the properties that you need.
 	spring.quartz.jdbc.schema=classpath:org/quartz/impl/jdbcjobstore/tables_@@platform@@.sql # Path to the SQL file to use to initialize the database schema.
 	spring.quartz.job-store-type=memory # Quartz job store type.
 	spring.quartz.properties.*= # Additional Quartz Scheduler properties.
+	spring.quartz.overwriteExistingJobs=false # Whether overwriting existing job definitions is enabled.
 
 	# REACTOR ({sc-spring-boot-autoconfigure}/reactor/core/ReactorCoreProperties.{sc-ext}[ReactorCoreProperties])
 	spring.reactor.stacktrace-mode.enabled=false # Whether Reactor should collect stacktrace information at runtime.

spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

@@ -5997,7 +5997,7 @@ provided with the Quartz library. It is also possible to provide a custom script
 setting the `spring.quartz.jdbc.schema` property.
 
 Quartz Scheduler configuration can be customized by using Quartz configuration properties
-()`spring.quartz.properties.*`) and `SchedulerFactoryBeanCustomizer` beans, which allow
+(`spring.quartz.properties.*`) and `SchedulerFactoryBeanCustomizer` beans, which allow
 programmatic `SchedulerFactoryBean` customization.
 
 NOTE: In particular, an `Executor` bean is not associated with the scheduler as Quartz
@@ -6030,6 +6030,15 @@ in a similar manner, as shown in the following example:
 	}
 ----
 
+Jobs created by configuration will not overwrite already registered jobs that have been
+read in from a persistent job store. To enable overwriting existing job definitions set
+`spring.quartz.overwriteExistingJobs` property:
+
+[source,properties,indent=0]
+----
+	spring.quartz.overwriteExistingJobs=true
+----
+
 
 
 [[boot-features-integration]]