GPII-539: Correct LifecycleManager's update method to apply live updates from PCP via Websockets

This pull request derives from http://issues.gpii.net/browse/GPII-539.

It is a small one, but given that https://github.com/GPII/prefsEditors/pull/66 is in, PCP's updates will actually be applied.

I've tested with the setup for the pilots: http://wiki.gpii.net/w/index.php/Cloud4all_Pilot_2_-_Set_up_and_installation

<b> Scenario for testing: </b>
- Set the machine up with "pilots2" branch of universal + these changes in LifecycleManager.js (currently me and @jobara have been having login issues with universal:master, we'll look deeper into this soon) and use this branch of mine for prefsEditors: https://github.com/radmanovi4/prefsEditors/tree/gpii-716 (this is GPII/prefsEditors#66)
- When testing on Ubuntu, there is a small fix you need to make to avoid error on login. You can see description by Javi in "[Architecture] Flow Manager: User login not working on Ubuntu" thread in architecture list.
- Open PMT and create a user ("save & apply" button)
- Switch to PCP ("quick editor" link)
- Make adjuster change and click "apply" button
Please refactor this as two separate tests (with appropriately shared configuration in a namespace) rather than issuing one test within the catch block of the other. Please also ensure that the "success" test verifies that some state has actually changed as a result of the update operation rather than just checking for the absence of a failure (currently a hole in our test coverage)