fixes #3821 Plugin menus are lost after page refresh in development

fixes #3587, #2855 - print an error on invalid json vs 500 error

fixes #3138 - move CR library loading into initializers, only show available providers

Fixes #2821 - Autoload paths, PowerManager children must be in namespace in order to autoload

fixes #2411 - add autoload_paths in application.rb in preparation for file location changes

fixes #426 expose BMC information in foreman UI

Signed-off-by: Ohad Levy <ohadlevy@gmail.com>

This patch also adds an abstracted power management class for both VM
and BM

fixes #2428 - a workaround for an issue with SETTINGS[:libvirt] not being properly initialized in rpm environments

fixes #2407 - Add STI to settings model

Also adds some tests for rendering new/missing STI models, and
refactors the old default_settings loader into the new sub-models.

upgrade foreman to rails 3.2.13

This commit updates from rails 3.0.x to 3.2.x, main changes include:

• Asset pipline support
• cleanup of existing assets (javascript, css, images)

Users who uses foreman in production, make sure that you now compile
your assets, e.g...

fixes #2239 API v2 CRUD for locations and organizations and added nested loc/org

bundler_ext initial support

This adds support for bundler_ext. The idea behind this is we want to avoid
Bundler in katello foreman builds, therefore in our RPMs we are gonna rename
Gemfile to Gemfile.in.

If Gemfile.in is found, bundler is not used and loading of dependencies is...

refs #1991 - Cache not cleared prevent location / org feature to show up

1. ensures settings cache is removed when app starts
we can't remove all cache, with Rails.cache.clear as that might lead to issues
with people using memcache with multiple foreman instances (e.g. we can clear...

fixes #1961 Adding JSONP support

When using cross-domain requests, it is impossible to read the response
data, and process it.
Using JSONP allows a client, from a specific domain (for example
/domain1), to query data in another doamin (/domain2), and analyze it,...

split api routes to separate routes file

[UI] fixes drop downs not showing up correctly when viewing a page with errors

dont fail if console bundler group is not installed

add more frendily error messages upon console failure

Allow to run rails console even if the support gems are not installed

adds ec2 provisioning support fixes #1223

- added progress bar for instance creation
- minor fixes for certname based deployments
- added ssh provisioning support to orchestartion, which utilize finish
scripts by default
- added images support (part of the vm compute tab)...

cleanups to rails 3 boot process

debian platform puppet is still considered a as a gem

ensure that bundler loads after our custom gem requirements

removed puppet from Gem file requirement

this commit also tries to simplify the way we use bundler, in future commits,
we should add more logic of which gems to load based on configration file.

Gemfile cleanups + adding some nicer console output

WIP rails3 migration