comps updates to add ceilometer_katello_dispatcher
fixes 3454 - changing default in UI to publish via http
Engine: Organization: deface core UI to include katello attributes

This commit contains changes that deface (extend) the core (foreman)
organization UI to include the following:

- on create:
  - label, description

- on edit:
  - label (readonly), description, default SLA
  - provide ability to download cert
Update to Engine Setup Readme
Engine: Removing old gem files
rabl-results - do not wrap outer collection
Merge pull request #3473 from thomasmckay/rabl-results

rabl-results - do not wrap outer collection
Engine: ignore api_version during auth rules checking

This change is to avoid the need to include 'api_version'
in controller param_rules, such as the one below.   If
api_version is not ignored, param rules evaluation will
fail with a 422 indicating 'Wrong parameters'

  def param_rules
    {
      :create => [:name, :organization_id, :provider]
    }
  end
Engine: UI: Fix the Sync Now on Repositories
Engine: API: fix issue with resource_list for api_version in resource

The API resources were recently updated to optionally include
the :api_version.  This broke the logic that returned
the list of resources in the resource_list api.  As a result,
subscription-manager commands (e.g. register, environments,
orgs) will not work.

This commit will ignore the :api_version in the RAILS
resources  when determing the list to return
as wellas omit it from the results sent to the
client.

For example, without this change, the API returns:
{'entitlements': '/api/entitlements/', 'status': '/api/status/', 'packages': '/api/packages/', 'consumers': '/api/consumers/'}

With this change, it will return:
{'status': '/api/status/', 'organizations': '/api/organizations/', 'roles': '/api/roles/', 'tasks': '/api/tasks/', 'sync_plans': '/api/sync_plans/', 'users': '/api/users/', 'distributors': '/api/distributors/', 'providers': '/api/providers/', 'entitlements': '/api/entitlements/', 'gpg_keys': '/api/gpg_keys/', 'repositories': '/api/repositories/', 'environments': '/api/environments/', 'content_views': '/api/content_views/', 'system_groups': '/api/system_groups/', 'products': '/api/products/', 'systems': '/api/systems/', 'changesets': '/api/changesets/', 'activation_keys': '/api/activation_keys/', 'content_view_definitions': '/api/content_view_definitions/', 'packages': '/api/packages/', 'consumers': '/api/consumers/'}
Merge pull request #3474 from bbuckingham/bug_fixes

Engine: 2 small bug fixes affecting product/provider/repo UI
Merge pull request #3475 from bbuckingham/fix-registration

Engine: API: fix issue with resource_list for api_version in resource
Serve Katello api documentation on '/apidoc` when Katello is loaded

We use the foreman `/apidoc` path to serve the Katello's resources
when the engine is loaded. This allows both Katello and Foreman
to use apipie for their bindings without affecting each other.

There are some issues with loaded the Katello code when loading
apidoc. One of the possible fixes is commenting out `wrap_parameters`
call in Foreman's `config/initializers/wrap_parameters.rb` file.
When doing that, http://localhost:3000/apidoc will serve as the
Katello's original apidoc path, using the api docs from the engine
Merge pull request #3471 from daviddavis/temp/20131206185141

Engine: Removing old gem files
Merge pull request #3364 from beav/comps

comps updates to add ceilometer_katello_dispatcher
Merge pull request #3476 from jlsherrill/3454

fixes 3454 - changing default in UI to publish via http
Merge pull request #3477 from iNecas/katello-apipie

Serve Katello api documentation on '/apidoc` when Katello is loaded
Merge pull request #3467 from bbuckingham/engine-orgs-deface

Engine: Organization: deface core UI to include katello attributes
paging-results - system groups apipie

paging-results - fixed parseInt()

paging-results - test cleaning

paging-results - fix angular tets

paging-results - damn rubocop
Bastion: Adds Grunt task to pick the proper library files for each
JavaScript library defined in bower.json in order to check the minimal
amount of third party libraries into source control.

Adds two new tasks for managing JavaScript libraries. The first,
'grunt bower:update' resolves dependencies listed in bower.json and
places the specified library files into the proper locations. This is
done because not all bower based libraries include only the needed files.
The task 'grunt bower:dev' is available for building the testing environment
and pulling down libraries needed for testing only.