Setting initial_action to fix create

Setting initial_action to edit to fix activation_key create behavior
custominfo-tupane-fix - fixed tupane layout for custominfo
Fixes #1661 - add request_type to notices retrieved using client polling

When client polled for notices, the 'request_type' was not included
in the json returned.  This addresses that issue.
distributors-minitest - systems and distributors testing

distributors-minitest - cleaned up based upon feedback

distributors-minitest - validators removed to support minitest restructuring, set/get now enforce these facts-backed params

distributors-minitest - sockets spec test incorrectly relying on facts, moved to minitest

distributors-minitest - minitest fix

distributors-minitest - fix for cached glue models

distributors-minitest - fixed missing vcr recording
Merge pull request #1647 from thomasmckay/distributors-minitest

distributors-minitest - systems and distributors testing
Merge pull request #1621 from daviddavis/cv_system_pgs

Content views: update list of content views on system new page
reduced the number of saves during default_content_view creation. KTEnvironment is now being saved only once.
updated db/schema.rb; removed default_content_view_id column from environments table
Merge pull request #1663 from bbuckingham/fixes_1661

Fixes #1661 - add request_type to notices retrieved using client polling
updated test fixtures after merge
env paths - sort paths by env name

This commit is provide a common behavior for the ordering
of the environment paths.

The initial issue observed was similar to:
 - paths:
   - dev, test, prod
   - dev-2, test-2

 - When a user would go to Changesets page, they would
   see the first path (dev, test, prod); however, the
   'next environment' would be dev-2.  The reason being
   the path ordering listed was sorted, but the determination
   of next environment used the paths unsorted.  This
   could result in the user creating a changeset and
   the content being promoted to dev-2; however, the user
   might assume it is going to dev, since that is the env
   path being displayed.

This change provides for a consistent behavior in the
various places where an env (or promotion) path is involved,
such as:
 - changesets
 - changeset history
 - activation keys
 - systems
 - organization
 ...
Merge pull request #1660 from daviddavis/act_key_create_fix

Setting activation_key initial_action to fix create behavior
content view - refactor add_content_view logic in controller to model

The controller has logic to when adding a content view to a
changeset, to also add the component views.  Refactored this
logic out of the controller and to the model so that it can
be leveraged by the API later.
allowing the use of repo set name for enable disable

and switching the cli to use the name
this will allow for easier automation,
since the set number will not need to be
looked up
Merge pull request #1652 from witlessbird/default_view_creation

reduced the number of saves during default_content_view creation. KTEnvironment is now being saved only once.
content views - fix changeset.add_content_view test
Fixes #1656 - Sets a minimum width on the body to reflect that hard width set on the content section.
remove old FIXME
Merge pull request #1665 from bbuckingham/sort_promotion_paths

env paths - sort paths by env name
Non action method in controller should be private