Promise Rejections and Performance

[matt4530]

Because NodeJS still has a performance hit for rejected promises, it may be wise to move away from a success or throwing a fail.

The current work around in Quartermaster is to set metronome.realSleepFrequency to some appropriate number, which allows the rejected promises to be processed multiple times during the simulation instead of after or after they have already piled up to a large number.

A fix like this would involve always having promises succeed and instead returning some response object, for which we can act on. The logic in each stage moves from try ... catch blocks to if ... else statements.