FLUID-4929: test case

Test case shows the test hanging when trying to test an event that is fired in conjunction with the component creation.
FLUID-4929: Implemented capability to bind IoC Testing fixtures to events which fire synchronously as part of a component's construction, by means of i) support for Luke Skywalker references to the target component, ii) improved framework support for cross-injection of "createOnEvent" specifications, iii) a new event fired by every TestCaseHolder named "onTestCaseStart". Took the opportunity to clean up the "activity" system without which this kind of issue is hard to debug - wrote a "standard activity record renderer" which essentially restores the kinds of "activity traces" that we would get before we had the big refactoring accompanying FLUID-4330. This will also be of use in the "Greeking and Scrobbling" system underway for visualising IoC activities. Restored the "fluid.browser" context tag which had been destroyed during the FLUID-4913 work as being apparently "redundant" when in fact it was the only tag of this type. This was causing the special QUnit-browser-directed UI provided by IOCTestUtils to not appear.
Merge branch 'master' into FLUID-4929
FLUID-4936: Refined logging system for fluid.log removes high priority console.log statements
Merge remote-tracking branch 'amb26/FLUID-4929'

* amb26/FLUID-4929:
  FLUID-4936: Refined logging system for fluid.log removes high priority console.log statements
  FLUID-4935: Fixed an issue with resolverSetConfig not propagating from rendererComponent options to its applier options.
  FLUID-4929: Implemented capability to bind IoC Testing fixtures to events which fire synchronously as part of a component's construction, by means of i) support for Luke Skywalker references to the target component, ii) improved framework support for cross-injection of "createOnEvent" specifications, iii) a new event fired by every TestCaseHolder named "onTestCaseStart". Took the opportunity to clean up the "activity" system without which this kind of issue is hard to debug - wrote a "standard activity record renderer" which essentially restores the kinds of "activity traces" that we would get before we had the big refactoring accompanying FLUID-4330. This will also be of use in the "Greeking and Scrobbling" system underway for visualising IoC activities. Restored the "fluid.browser" context tag which had been destroyed during the FLUID-4913 work as being apparently "redundant" when in fact it was the only tag of this type. This was causing the special QUnit-browser-directed UI provided by IOCTestUtils to not appear.
  FLUID-4929: test case