Merge pull request #1557 from bbuckingham/fork_content_views_fencing

content views - ui - minor changes on the nav
Content views: updating content views and products on activation key page
Merge pull request #1558 from bbuckingham/fork_content_views_jslint

content views - address jslint warnings
Merge pull request #1548 from daviddavis/cv_act_key_field

Content views: updating fields on activation key page
content views - composite - disable publish/refresh on invalid definition

There are cases where a composite definition can become invalid.
When that happens, we don't want to allow the user to publish
another view off of that definition or refresh existing views,
until the definition has been fixed.  This commit simply
disables the publish/refresh actions and provides the user with
a tipsy letting them know of the error.  There will be additional
changes coming to allow them to actually 'fix' the definition.

An example where this could occur:
- view1 has repoA
- view2 has repoB
- composite definition 'compositeDef' created with view1 and view2
- composite definition published to compositeDef published to
  'compositeView'
- the definition for view1 is updated to include repoB and
  view1 is refreshed

- at this point, publishing compositeDef or refreshing
  compositeView would be invalid, because having the same
  repo in multiple component views is not allowed....
content views - address comments on PR 1549

Minor changes to address pull request comments.