Convert UpdateManager to a singleton.

## Why
There should only be one UpdateManager in Dynamo.

## How
* The UpdateManager is made a singleton and its required reference to a DynamoModel object is removed.
* All tests for the UpdateManager have been fixed, and their speed has been greatly improved by testing the UpdateManager in isolation. We no longer need to start Dynamo to conduct these tests.
* All UI tests for the UpdateManager are fixed by mocking the singleton. These tests have been removed from the "Failing" category.
* As part of the DynamoModel refactoring and also as part of this pull request, data bindings were broken between the GraphUpdateNotificationControl (the little green cloud), and its data source which should now be the singleton UpdateManager. These data bindings are now fixed.

This pull request addresses internal issue:
http://adsk-oss.myjetbrains.com/youtrack/issue/MAGN-4224

@pboyer PTAL
For the record, I move a lot of the more complex method calls in the constructor into helper methods just for readability.  This is sort of problematic because they could be called more than once.  I guess it's okay you changed this - just wanted to make my intentions clear.