Plugin for toggling visibility on cluster deploy

We need to show/hide certain parts of barclamp configuration only when a
cluster is deployed. This jQuery plugin adds that functionality.

Example usage:

<fieldset data-elements-path="database-server" data-show-for-clusters-only="true">

This element (and its children) will be shown only when:

1. A cluster is already part of a deployment
2. A cluster is dragged into the node list

The data-elements-path specifies where to check in the deployment JSON
for already deployed clusters. data-show-for-clusters-only enables this
plugin for a given element.
Add huge fixme
Initialize cluster conf plugin in application.js
isCluster matches on ":" instead of "cluster:"

as suggested by @tboerger
Add helper for finding unclaimed drives

This is a prereq for cinder to check if any disk-backed volume can be
created.
Merge pull request #999 from bkutil/show_for_clusters

Plugin for toggling visibility on cluster deploy
Handle removed node referenced by another proposal

When another proposal removes a node which the current proposal
references, the corresponding DOM element is no longer available in the
deployment list. However, info from this element is needed by the
nodeList, when it triggers an event that a node has been removed.

Make the nodeList look up the info in some other way.
Merge pull request #1001 from bkutil/unclaimed_drives_helper

Add helper for finding unclaimed drives
Merge pull request #1003 from bkutil/handle_nodes_removed_from_role

Handle removed node referenced by another proposal
dynamicTable overwrites changes w/ old data

BNC#865526

The dynamicTable plugin caches the proposal attributes JSON in it's json
property and does not take into account that the data might have
changed when it writes its own copy back.

This fix minimizes the race window. Another one would be to
make sure we always operate only on the path + value that changed.
webui: Sort clusters in the list of clusters
Merge pull request #1008 from vuntz/sort-clusters

webui: Sort clusters in the list of clusters
Do not rely on TCP keep-alive for running commands through ssh

The timeout for this is huge (not sure how big, but certainly more than
10 minutes). This is extremely bad when we run chef-client over ssh
while applying a proposal because if the host goes down, we will be
totally blocked for too long. This happens even more since we have HA
and STONITH can kill nodes.

Instead, we use the ServerAliveInterval=15 option, which means we use a
ssh-internal mechanism for a 15s timeout. It will try this three times,
resulting in a 45s timeout before giving up. This is largely enough in
the context of crowbar.
Merge pull request #1010 from vuntz/ssh-serveralive

Do not rely on TCP keep-alive for running commands through ssh
Merge pull request #1006 from bkutil/dynamic_table_race

dynamicTable overwrites changes w/ old data