It should not be possible to start JobScheduler with options -exclusive and -distributed-orders together

Load balancing cluster (-distributed-orders) and backup cluster (-exclusive) are two different methods to run JobScheduler in a cluster but there are not working together. Both methods are using the scheduler_id to identify the cluster, therefore they are mutually exclusive.

JobScheduler should not start and throw an exception if it tries to start with both options.