Improvement of Issue: "It should be possible to define different color schemes for Primary and Backup JobScheduler"

Current Situation

JOC Cockpit reads the precedence attribute in the ./switch response to know which Cluster member of a Passive Cluster is active.

JOC Cockpit doesn't know the precedence after a normal login and if the active Cluster Member is changed during an active session.
In both cases JOC-139 doesn't have an effect.

Desired Behavior

• If the active Cluster Member is changed during an active session then the ./events web service response contains a CurrentJobSchedulerChanged event and JOC Cockpit should call the ./jobscheduler web service (only with the "jobschedulerId" in the body) to know the "clusterType" and the "precedence" of the current JobScheduler (see also JOC-283).
• After a login or a switch then JOC Cockpit calls already ./jobscheduler/ids which can be used to read the precedence