refactor: config duplication and fetch-and-lock-on-execute ambiguity in spring config are fixed

Author: strelchm

README.md

@@ -276,7 +276,7 @@ as they do not support descending indexes.
 #### Polling strategy
 
 If you are running >1000 executions/s you might want to use the `lock-and-fetch` polling-strategy for lower overhead
-and higher throughput ([read more](#polling-strategy-lock-and-fetch)). If not, the default `fetch-and-lock-on-execute` will be fine.
+and higher throughput ([read more](#polling-strategy-lock-and-fetch)). If not, the default `fetch-and-lock-on-execute` (configured as `fetch` in Spring Boot) will be fine.
 
 :gear: `.pollUsingFetchAndLockOnExecute(double, double)`<br/>
 Use default polling strategy `fetch-and-lock-on-execute`.<br/>
@@ -452,9 +452,6 @@ db-scheduler.enabled=true
 db-scheduler.heartbeat-interval=5m
 db-scheduler.missed-heartbeats-limit=6
 db-scheduler.polling-interval=10s
-db-scheduler.polling-strategy=fetch
-db-scheduler.polling-strategy-lower-limit-fraction-of-threads=0.5
-db-scheduler.polling-strategy-upper-limit-fraction-of-threads=3.0
 db-scheduler.table-name=scheduled_tasks
 db-scheduler.immediate-execution-enabled=false
 db-scheduler.scheduler-name=
@@ -464,7 +461,7 @@ db-scheduler.priority-enabled=false
 # Ignored if a custom DbSchedulerStarter bean is defined
 db-scheduler.delay-startup-until-context-ready=false
 
-db-scheduler.polling-strategy=fetch
+db-scheduler.polling-strategy=fetch # fetch-and-lock-on-execute (default)
 db-scheduler.polling-strategy-lower-limit-fraction-of-threads=0.5
 db-scheduler.polling-strategy-upper-limit-fraction-of-threads=3.0