* Fix DataService so that it honors labelSelector on list
* Fix ApplicationsService to use the correct label selector
  for replicationcontrollers

Bump to 0.0.58

Bug 1493439 - Remove the canI check for secrets from bind-result

The `canI` check only works if you've visited the project. This is not
always true when provisioning from the catalog, so it means the secret
is sometimes not displayed as a link when it should be.

To provision a service or create a binding with parameters, it's
required that the user create secrets anyway, so the check should never
fail is permissions are set up properly.

If the user doesn't have authority, the worst that happens is that they
see a permission denied error following the link. In practice, it
shouldn't happen.

https://bugzilla.redhat.com/show_bug.cgi?id=1493439

Add `watch` to package.json

Set guided tour close button styles, override hopscotch image setting.

Bump to version 0.0.57

Add apiService.getPreferredVersion, and constant apiPreferredVersions

Use label selectors in ApplicationsService

Filter out replication controllers and replica sets that have owners
using label selectors in calls to `DataService.list`.

Update patternfly version

 update kubernetes-label-selector as well to avoid patternfly version
conflicts.

Add ui config for notifications

- notification.showInDrawer defaults false
- notification.skipToast defaults false

Bump to version 0.0.56

Adopt new service catalog resource names

Instance -> ServiceInstance
Binding -> ServiceInstanceCredential

Don't show redeploy message if not binding to an application

Don't show a user the message saying they need to redeploy their app if
they haven't bound the service directly to an application.

Bump version to 0.0.55

Fix runtime error binding to app

Update notification id to unique id specifically for  in templates

Add ApplicationsService utility to retrieve all 'applications' for a project

Version bump to v0.0.54

Improve notification id

Fix bug where long project names cause scrollbar in add modal

- _.uniqueId() is not sufficient since the ID is used to persist some data
  for notifications via session storage.  The id generated starts at a low
  number & increments w/o randomness.
- Using _.uniqueId() along with Date.now() adds a random value that cannot
  be replicated across sessions/refresh

Bump version to 0.0.53