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
 ...
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
Fixes #1656 - Sets a minimum width on the body to reflect that hard
width set on the content section.
Merge pull request #1667 from ehelms/menu-fix

Fixes #1656 - Sets a minimum width on the body to reflect that hard
Merge pull request #1665 from bbuckingham/sort_promotion_paths

env paths - sort paths by env name
fixing descriptions and spacing
Merge pull request #1666 from jlsherrill/set_id_to_set_name

allowing the use of repo set name for enable and disable
routes.js - regenerating

a recent commit removed several routes from routes.js...
Merge pull request #1676 from bbuckingham/fix_routes

routes.js - regenerating
db-seeds-headpin-fence - fence pulp call
Merge pull request #1677 from thomasmckay/db-seeds-headpin-fence

db-seeds-headpin-fence - fence pulp call