Card 276

Basic functionalities to pull 'publish-gear-endpoint' logic into the platform.
In doing so, we now use 'connection-type' argument to ensure that we check both the connection name and the type.
Bug 956050
Bug 956050
Bug 957221 - Query local mirror, then remote mirror

* Update based in V2 work
Implement multi-versioned jbossews-1.0/2.0 v2 cartridge
Removed 'setmaxstorage' option for oo-admin-ctl-user script.
Added 'setmaxtrackedstorage' and 'setmaxuntrackedstorage' options for oo-admin-ctl-user script.
Updated oo-admin-ctl-user man page.
Max allowed additional fs storage for user will be 'max_untracked_addtl_storage_per_gear' capability + 'max_tracked_addtl_storage_per_gear' capability.
Don't record usage for additional fs storage if it is less than 'max_untracked_addtl_storage_per_gear' limit.
Fixed unit tests and models to accommodate the above change.
fix for bug#956117 - cartname is required for start/stop and not comp_name
Modifying cron cartridge to point to correct limits and frequencies location
Changed echo to client_result in cron cartridge
Removed unused jobs from cron cart. This lives in the platform now
Removed empty dirs from cron cartridge
Card online_runtime_266 - Renamed OPENSHIFT_<short name>_PATH to OPENSHIFT_<short name>_PATH_ELEMENT
Make this call less chatty.
The teardown hook needs gear unlock.
Bug 957257 - use an internal function to get the MCS label.
origin_runtime_127: Add X-Request-Start header.
Add /health url to php cartridges.
Fix v2 model unit tests.
Merge pull request #2201 from BanzaiMan/dev/hasari/c276

Merged by openshift-bot
<cache> bug 957818 - clear-cache script, oo-cart-version uses it

https://bugzilla.redhat.com/show_bug.cgi?id=957818
oo-cart-version was making some assumptions that didn't work across
projects or usage. It should not assume it is run on the broker, and
it should not assume development mode.

Dealing with clearing cache generically across projects is annoying
enough that I added a script to do it. oo-admin-broker-cache is aware
of SCL and loads the broker rails environment (which is of course aware
of dev/prod mode) to clear the cache.
We should never again need to explain this to people who just want to
clear their cache.

oo-cart-version now can just call this script, if it is even run on a
broker. If it isn't, which is the normal case, it can give the user a
simple command to run themselves.