Refactor Deployment pointers to treat snapshots like a linked list [2/2]

This refactoring greatly simplifies how deployments are managed by Crowbar.  It was orginally a longer term design objective,
but streamlined the code when we pulled it in.

Basically, we are now treating snapshots like a linked list instead of 3 descrete pointers.  The deployment has a pointer
to the head of the list (which is the proposal/committed/active snapshot).  When a new proposal is needed, we simply add 
to the head of the list and move the deployment pointer. 

Consequently, the STATUS information is much much easier.  We do NOT use deployment pointers for status, we get it directly
from the node roles attached to the head of the deployment.

Victor and I felt in discussion that this was easier to explain and much more "truthy" about the actual state.

It also made the code smaller.  Profit!

This code includes another MILESTONE... from the UI, you can now commit, anneal and then propose a deployment.

PLEASE READ THAT AGAIN > you can now commit, anneal and propose a deployment in cycle.

One last goodie - I have a bunny refresh candidate (CB2 only).  Feedback welcome.


 .../barclamp_test/node_roles/_test-admin.html.haml |    2 +-
 .../node_roles/_test-client.html.haml              |    2 +-
 .../node_roles/_test-discovery.html.haml           |    2 +-
 .../node_roles/_test-library.html.haml             |    2 +-
 .../node_roles/_test-server.html.haml              |    2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

Crowbar-Pull-ID: 19f38c540a236355f057e8c118e2f30804325799

Crowbar-Release: development