Flowable Timer Start Event not auto deleted when there is new deployment version

Dieses Issue hat noch niemand übernommen.

```text
*Timer Start Event*
Description
A timer start event is used to create process instances at given time. It can be used both for processes that should start only once and for processes that should start in specific time intervals.
Note: a sub-process cannot have a timer start event.
Note: a start timer event is scheduled as soon as process is deployed. There is no need to call startProcessInstanceByXXX, although calling start process methods is not restricted and will cause one more starting of the process at the time of startProcessInstanceByXXX invocation.
Note: when a new version of a process with a start timer event is deployed, the job corresponding with the previous timer will be removed. The reasoning is that normally it is not desirable to keep automatically starting new process instances of the old version of the process.
```
Hi Flowable,
I impemented a start timer event with recurring schedule, but I found that the older version timer job was not auto removed. it causes there are some timer jobs in the flowable engine running concurrently. but according to above "Note", the start timer job will be replaced by newer version.

0 0/5 * * * ?

Beginnen Sie damit, das wiederkehrende Timer Start Event aus dem bereitgestellten BPMN XML zu reproduzieren, indem Sie eine Prozessversion und anschließend eine neuere Version bereitstellen. Verfolgen Sie den Lebenszyklus des Timer-Jobs während der Bereitstellung und überprüfen Sie, dass der Job der vorherigen Version entfernt wird, sodass nur der neuere Timer aktiv bleibt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.