fixes #6322 - clean up puppet environment on cv delete

Attempt to move content host's hosts.  If there are others left
or host groups attached, throw a nice error.  In the future
we should add host and host group puppet environment selection
to the content view version deletion
fixes #6603 / BZ 1115341 - content search - fix for missing package metadata

This commit is to address errors that could occur if the package
metadata was missing information for fields such as, provides,
requires, files or changelog.
Fixes #6623 - Candlepin dependency correction for RHEL 7
Fixes #6272/BZ1118479 - move Bastion guide to katello.org.

Move Bastion documentation to katello.org. These links will
point to the github files themselves for now and will be
updated once the docs site is live.

http://projects.theforeman.org/issues/6272
https://bugzilla.redhat.com/show_bug.cgi?id=1118479
Fixes #5952, BZ1079174 - Fixes issue with content view filter name and description being impossible to edit
refs # 6720 - necessary apidoc changes for content-management, BZ 1105276
fixes #6719 / BZ 1079953 - Content Notices - fix deletion and list by org

This commit addresses 2 issues w/ the content notices page:
1. list only the notices associated with the current org
2. update so that clicking 'Delete All' will render the confirmation dialog
Fixes #5858,bz 109961 - Updated cv published content count

After a content view is published, the package/errata counts of the
newly created content view version was not getting updated in the ui.
This commit aims to fix that by forcefully reloading that specific
version of the content view when the publish is completed.
fixes #5096 - fail gracefully on pulp repo creation failure

The goal is to run the action creation in the plan phase
and error out if its not valid.  A similar approach is taken
with Content Host Creation.  However in that case, content hosts
are not created in other situations.  Repositories are created during
publish/promote of content views as well and in that situation we do not
want to perform pulp creation in the plan phase.  As a result I have created
a new action CreateImmediate that does the creation in the plan phase.
It attempts to use as much from Create as possible (there is a lot of code there)
Fixes #5985/bz1102120 - Marked content_view_id as required param

Content VIew id is marked as required param in the docs
for the cv filters index call but nothing is enforcing that.
This commit handles that enforcement aspect
fixes #6737 - correct 'automatic' amount for subscriptions
fixes #6740 - cleared up enabled text
fixes #6596 - fixes #6596 - change 'type' method to 'system_type' in Katello::System
Merge pull request #4469 from bbuckingham/issue-6719

fixes #6719 / BZ 1079953 - Content Notices - fix deletion and list by org
Merge pull request #4423 from bbuckingham/issue-6603

fixes #6603 / BZ 1115341 - content search - fix for missing package metadata
Merge pull request #4421 from isratrade/6596

fixes #6596 - change 'type' method to 'system_type' in Katello::System
Merge pull request #4456 from jlsherrill/5096

fixes #5096 - fail gracefully on pulp repo creation failure
Fixes #6647,BZ1120335 - Remove old foreman org destroy routes

Removing old foreman destroy routes since they don't use dynflow to delete
organizations.
Fixes #6759/BZ1108928: using #content as topbar.js expects.

Foreman's topbar.js expects an element with an id of "content"
that it adds top padding the size of the header to in order for
there to be sufficient room for the floating header.  This commit
renames #maincontent to #content so Foreman's topbar.js works for
katello pages.

http://projects.theforeman.org/issues/6759
https://bugzilla.redhat.com/show_bug.cgi?id=1108928
Refs #6696 - Fixing test that doesn't work with content-type json

Due to a change in foreman, we're using json for all api requests (which is the
only supported content-type for the api) and this triggers wrap_parameters.
With wrap_parameters, since organization_id is a product attribute, we no
longer hit the bad request. If we remove organization_id though, then we hit
404. So basically, there's no way to hit a 400 error. An alternative would be
to remove this test.