fixes #6120 / BZ1102963 - address error during content host bulk actions

When performing a bulk action (e.g. pkg, pkg group or errata
install/update/remove) action, the user would get an error similar
to the following:

    TypeError: can't convert Symbol into Integer
    katello/app/lib/katello/bulk_actions.rb:94:in `[]'
    katello/app/lib/katello/bulk_actions.rb:94:in `save_job'
    katello/app/lib/katello/bulk_actions.rb:35:in `block in install_packages'
    katello/app/lib/katello/bulk_actions.rb:88:in `perform_bulk_action'
    katello/app/lib/katello/bulk_actions.rb:33:in `install_packages'

The cause of the error is that pulp 2.4 changed the response to consumer group
actions; however, the bulk actions had not been updated for this change.
In pulp 2.4, the response no longer returns a 'job' along with 'tasks'
associated with that job.  Instead, it returns a list of tasks that the user
must individually monitor.

Since the content host and host collections UIs no longer provide the
user a way for a user to see pulp job/task information (i.e. this was
removed in favor of using dynflow and displaying it's task info), this commit
removes the saving of the pulp job/task information on bulk actions.

In a future commit, we'll update the bulk actions to utilize
dynflow, so that a user can see details on the actions performed.
In the meantime, the user can see updates by looking on the affected
content hosts or via changes to the content hosts package profiles
(after uploads that occur after the bulk actions are performed).
Fixes #5162/BZ1096407 - fix setting of sync time for new sync plans.
Fixes #5552/BZ1093751 - Prevent sorting on columns that aren't sortable.
fixes #5974 / BZ1098165 - content host - fix issue with spinner on package deletion

Prior to this commit when a user would click the (X) to delete
a package, the the (X) would turn in to a spinner and spin forever.
Although, this occured, the package would actually be deleted from
the client (content host).

This commit contains a few changes:
1. Update the behavior of deleting a package to be consistent with
   the other supported actions.  This basically means to take the
   user to the dynflow tasks pane which shows the status/progress
   of the deletion.
2. Remove the existing 'ContentHostTask' logic.  Since the content
   host actions are all dynflow, this logic is no longer used/needed.
3. Update the humanized input of the task to handle the fact that
   when a package is deleted using the list it isn't deleted based
   upon only the package name, but by a hash consisting of
   name+version+release+arch.
4. Add an error handler to show any errors from the server when
   the action request is initially sent.
Fixes #5719 - make pulp async actions cancellable

The cancelling is done though the task details: running steps tab
Merge pull request #4232 from waldenraines/5162

Fixes #5162/BZ1096407 - fix setting of sync time for new sync plans.
Merge pull request #4235 from waldenraines/5552

Fixes #5552/BZ1093751 - Prevent sorting on columns that aren't sortable.
Fixes #5761, #5899 - Update Katello kickstarts

This change brings the Katello kickstarts forward to match what's in the
Foreman community versions, with the community yum repos removed as Katello
will manage content.

This includes the security hardening in #5895, and Realm integration from
Refs #6123,BZ1106563 - Disabling org deletion

We're not supporting deleting orgs in the next release so this change will
temporarily disable that functionality until then.
fixes #6151 - filter content-views by name for hammer, BZ 1107319
fixes #6108/BZ 1105310 - ensure unique name when creating installation media

When publishing a kickstart repository (which could be the result of syncing the repo or publishing it as part of a content view), installation media will be created.

The media name currently uses the following convention:
   org.label/lifecycle_environment.label[/content_view.label] distro.family distro.variant distro.version distro.arch

For example:
   ACME_Corporation/Library RedHat Server 6.5 x86_64
   ACME_Corporation/Library/ks_view RedHat Server 6.5 x86_64

The current convention can cause name conflicts when creating the media as both the 6Server and 6.5 kickstart repos have distro.version of "6.5"; however, they are 2 separate repos/media from a content management point of view.

In order to address this, this commit modifies the naming convention to the following:
   org.label/lifecycle_environment.label[/content_view.label]/repo.label

E.g:
   ACME_Corporation/Library/Red_Hat_6_Server_Kickstart_x86_64_6_5
   ACME_Corporation/Library/Red_Hat_6_Server_Kickstart_x86_64_6Server
Merge pull request #4243 from komidore64/rmi6151-content-view-filter-name

fixes #6151 - filter content-views by name for hammer, BZ 1107319
Merge pull request #4227 from bbuckingham/issue-6108

fixes #6108/BZ 1105310 - ensure unique name when creating installation media
Merge pull request #4231 from bbuckingham/issue-6120

fixes #6120 / BZ1102963 - address error during content host bulk actions
Merge pull request #4237 from bbuckingham/issue-5974

fixes #5974 / BZ1098165 - content host - fix issue with spinner on package deletion
fixes #6168 - subscription list should require org, BZ 1097647
Fixes #6146 BZ1105623: Fixing undefined method call

Fix undefined call to "get_content_view_environment_by_cp_id" in systems
controller.
Merge pull request #4242 from daviddavis/temp/20140610140413

Fixes #6146 BZ1105623: Fixing undefined method call
Fixes #6153, bz1107876 - Fixed cv package excludes publish

Previously if you published a content view with a package excludes
filter with a matching package in the repo. You would get the following
error from pulp (package name is gofer in the example)
pulp.server.webservices.controllers.repositories:ERROR: Error parsing
unassociation criteria [{'fields': {}, 't
ype_ids': ['rpm'], 'filters': {'$or': [{'filename': {'$in':
['gofer-1.2.0-1.el6.noarch.rpm']}}]}}]

This commit fixes that issue.

more
Fixes #6171: Remove nil UUIDs when generating content host list.

The presence of nil UUIDs will cause ElasticSearch to fail when fetching
and thus no content hosts will be returned when hitting the index API method.
Content hosts with nil UUIDs can occur when an error occurs in a backend
system during content host registration.