FLUID-4525: Removed included infusion files from the fat panel iframe. As a result, theOtherWorld component is demolished from the fat panel. UI Options interface is now successfully rendered into iFrame by using the outer world jQuery and infusion. The remaining issues are, 1. the UI is not properly distributed into each tab; 2. Utilize the page enhancer in the outer world to manipulate the main page and iFrame content.
FLUID-4525: Fixed the issue that the UIO tabs are not rendered properly as well as namespacing a couple of fatPanel sub-components into fluid.uiOptions.fatPanel.
FLUID-4525: "jQuery bus" through core framework now resolves issue with broken sliders in UIOptions. Impl is still full of detritus and needs a lot of cleaning
FLUID-4525: Slightly simplified implementation with dead code removed and direct references to uiOptions subcomponents ("proto-ants") removed from FatPanel. Renamed "markupRenderer" as "iframeRenderer". Next step is to knock together "fatPanel" and "fatPanel.renderUIOptions"
FLUID-4525, FLUID-4028, FLUID-4398, FLUID-4337, FLUID-4151 - New simplified implementation for FatPanel UIOptions using new "composite event" and "boiled listener" facilities from FLUID-4398 and FLUID-4337. Improved diagnostics in framework - every event fired is now logged with its source and listener count. Previous verbose "demands resolution" logging is now prevented by dedicated flag. FatPanel opens and operates again but probably harbours severe bugs especially wrt. options parsing and UIEnhancer. Further work needed in core UIOptions to further simplify it in light of new event facilities. Tests required for "local event resolution" and also for previous jQuery injection functionality.
FLUID-4525, FLUID-4398, FLUID-4338 - first version of "simplified FatPanel" that appears fully working in the UI. Many adjustments in the core framework for "jQuery cascade" - the first instance of a component bearing a "jQuery" option will be diverted to use this to form its container. All subsequent containers formed by DOM binder location will automatically cascade that jQuery to their own containers. It is still necessary to explicitly supply the option to a renderer-bearing component. Fix was required in autobind to correctly use custom jQuery and document. This should really be fixed to indirect off the jQuery object holding "node" (assuming it is one - this would amount to an API change). Next step - get all test cases working again and normalise use of "prefix"
FLUID-4525, FLUID-4398: All test cases passing again for UIO. Test cases tidied to avoid including UI plugins in "outer world" to verify correct jQuery cascading. Finished correcting SlidingPanel impl to model-driven version. Base UIO further tidied to remove messy "event relay". Test cases still required for FLUID-4338 as well as new "jQuery cascading".
FLUID-4525, FLUID-4536, FLUID-4338: Further simplification of cross-iframe strategy - now simply a "container with foreign jQuery" is enough guidance for the renderer, etc. in a full subtree. Discovery and fix for corruption in "mapOptions" in UIOptions which was failing to remove mapped material from its old location, leading to a complete duplicate set of components being constructed. This was being masked by an unexpected route for IoC resolution, also affecting "prefix" for ToC component. Test cases for cross-iframe FLUID-4536 and IoC FLUID-4338 fixes.
FLUID-4532: Reverting ARIA labeller component to pre-IoC strategy
FLUID-4537: Further fixes to allow path values to be resolved when raw reference to "pathAs" is issued from light material. Modified test case as supplied by JURA.
Merge branch 'FLUID-4525' into shadow

Conflicts:
	src/webapp/tests/framework-tests/renderer/js/RendererUtilitiesTests.js
Merge branch 'FLUID-4537' into shadow

Conflicts:
	src/webapp/tests/framework-tests/renderer/js/RendererUtilitiesTests.js
Merge branch 'FLUID-4532' into shadow
FLUID-4539: Fix for greedy stringTemplate implementation through key sorting
FLUID-4564: New rationalised implementation of listener merging, common across lifecycle functions and standard events. Resulting simplified implementation of component option merging with fewer special cases, ready for grade caching work. Also rationalised implementation of merge policies - these are now invoked in a standard way at a single workflow point in mergeImpl. New global name for fluid.makeEventFirer and simple utility fluid.fireEvent
FLUID-4539: Fix to fluid.stringTemplate caused a regression in LayoutReordererTests. The feared case has finally bitten, and the strategy used in fluid.isArrayable has to be judged inadequate (it is over-broad). The "elementIndexer" for ModuleLayout returns a structure with an element named "length" which meets the criteria for being arrayable, in that it has a member named "length" which is of type number. This leads to a corrupted message when this structure is used as an argument to the new stringTemplate which passes it to framework utility fluid.keys. New implementation uses a strategy cobbled from an earlier version of jQuery, together with an explicity check for jQuery objects. The only case which cannot be saved is "arguments" which can't be reliably detected cross-browser. We need to drop any raw uses of "arguments" throughout the framework and instead always convert explicitly using fluid.makeArray.
Merge branch 'shadow' into FLUID-4564
FLUID-4564: Fixed up UploaderCompatibilityTests comparison for new listener merging strategy. After one pass through merging, listeners will always consist of an array.
FLUID-4338, FLUID-4193: Fix for FLUID-4338 using "pathUtil" utility creates dependency of IoC on DataBinding.js - added in to test cases where missing. Also fix for what looks like nondeterministic failure of earlier fix for FLUID-4193 - "container" argument accumulated all decorated nodes for that cutpoint so far rather than just containing exactly the node for this match.
Merge branch 'FLUID-4525' into shadow