When deleting a custom event the wrong JobScheduler instance can be addressed

Current Situation

If more than one JobScheduler instance is installed and each instance has its own Event Processor job chain then the list of events can contain events from more than one event processor. When deleting an event that is not assigned to the current JobScheduler instance then the delete command fails as the event is not known in the current event processor.

Desired Behaviour

When deleting an event the JobScheduler ID that is stored in the events database should be used to identify the responsible event processor. Also the event should be deleted from the database even if there is no event processor assigned with the given JobScheduler ID.