pulp peformance enhancements
using bulk_load_size config option for determining bulk loads
content views - ui - composite view promotion - help users with component views

When promoting a composite view to the "dev" environment,
the process basically takes the version of each of the
component views that is in "dev" and generates a new
composite view in "dev" from those components.  This
requires that all of the component views have already
been promoted to dev.

In order to simplify this process for the user, this
commit performs the following:

- if the user adds a composite view to a changeset, automatically
  add any component views to the changeset that have neither
  already been promoted to the next environment nor have been
  added to the changeset.  This will only be done for those
  component views that the user has permission to promote.
  The user will be informed via a 'message' notice of
  and component views that were added to the changeset for them.

- if the user later removes one of those component views, when
  they attempt to promote the changeset, generate an error
  to inform them of the need to also promote the component
  view
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
 ...
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
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
katello-configure - Include param name into wrong param error message

Compare:

     Option: [Katello user's password] not correctly specified.

with

     Option: [Katello user's password (--user_pass)] not correctly specified.
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
Non action method in controller should be private
Local variables snake_case instead of CamelCase
Use snake_case instead of camelCase for method names
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
Refactored system template specs

Test now uses factory girl. Also make use of let helper instead of
before each which is lazy evalued. Clean lazy attributes from Repo that
are not used anymore after Pulp v2 migration.
Remove expectations on nil warnings

When running all rspecs somewhere in the middle were displayed warnings
that you are expecting message receive on nil objects. This was caused
by wrong variable names in systems_controller_spec.
Fix ping spec

Headpin ping spec was not set in headpin mode so it tried to contact
Pulp. I DRYed up this spec and added config stubbing so it works
correctly.