If NXRM is read-only or lacks quorum, then run now triggers make startup fail.

When NXRM starts up, it reattaches job listeners.  Part of doing that is checking for jobs with a Run Now Trigger and scheduling them for execution.  If NXRM boots in read-only mode or lacks quorum, then startup fails.  This is very similar to the linked issue, just for a different method in the quartz scheduler.  

Acceptance Criteria:  

If an exception is thrown during scheduling a run now job, then NXRM can still start up. 

Added new constants to https://docs.google.com/spreadsheets/d/1ttdwZnMf-gzfufW5dQdyowmxyZ7JvLywJr45eN26UaU/edit#gid=0

Stack Trace: 

2019-01-15 20:22:15,491+0000 ERROR [FelixStartLevel] Node1 *SYSTEM com.orientechnologies.orient.core.db.OPartitionedDatabasePool$DatabaseDocumentTxPooled - Error on transaction commit `7D81AA6B`
com.orientechnologies.orient.server.distributed.ODistributedException: Quorum (2) cannot be reached on server '8DB6E7C3-2EEE050D-5FCB6C5F-8683E9D8-C95CD3C4' database 'config' because it is major than available nodes (1)
 at com.orientechnologies.orient.server.distributed.impl.ODistributedDatabaseImpl.calculateQuorum(ODistributedDatabaseImpl.java:1055)
......
 at org.quartz.core.QuartzScheduler.rescheduleJob(QuartzScheduler.java:1115)
 at org.quartz.impl.StdScheduler.rescheduleJob(StdScheduler.java:321)
 at org.sonatype.nexus.quartz.internal.QuartzSchedulerSPI.reattachJobListeners(QuartzSchedulerSPI.java:356)
 at org.sonatype.nexus.quartz.internal.QuartzSchedulerSPI.doStart(QuartzSchedulerSPI.java:198)
.......