content views - migrating default content view structure

previously each environment had its own default
content view with a single version.  This migrates the data
and code such that each org has a default content view
and each environment has a content view version within the orgs
default view.

This was mainly done because content search makes much more sense
when the default view is organized this way
896147 - Notify user of keyname presence when adding
default_system_info to an org
test fixes
merge conflict fix
fixing methods that were moved
making tests happy
923112 - Katello Nightly : Add,Apply.Remove default custom info
keynames for subscriptions that are set at the organization level failed
via Cli
(cherry picked from commit ad57ee9a431321aeb64e68d805abeb5ec1c93c3d)

Conflicts:
	src/spec/controllers/api/organization_default_info_controller_spec.rb
fixing space issues
adding oddly missing migration
super happy tests
test fixes
merge conflict fix
test fix
vcr update... again
Make oauth working

Use Rack::Request (supported by the oauth gem) instead of
ActionDispatch::Request (not supported by the gem).
Include candlepin info about pools in activation keys details

Needed by foreman-katello-engine to display activation keys details.
adding addition ktenvironment tests
fixture update... yet... again
test fixes
Merge pull request #1773 from jlsherrill/default_view_change

 content views - migrating default content view structure