Updates jQuery framework to 1.8.3 and removes buffered jQuery.

Buffered jQuery theoretically improves performance by grouping all DOM manipulations through jQuery into a queue that can be flushed at once, but this needs to be benchmarked to be properly understood.
Fixes styles application after changes and updates tests to match changes with jQuery styles.
Gets rid of deprecated code and warning on IE.
Patches jQuery to prevent security exceptions in IE.

This does NOT patch jQuery to make all calls to .append(), .insert(), etc. pass security validation in IE.  Instead it uses toStaticHTML (as recommended by Microsoft) to strip 3 innerHTML strings used within jQuery for testing.
Changes the patch of jQuery to use execUnsafeLocalFunction, which doesn't alter the test HTML used by jQuery and therefore should not effect the outcome of the jQuery tests while still removing the annoying IE warnings.
Added platform detection for the Apache Cordova (formerly phonegap)
javascript-to-mobile bridge. Also added gitignore entries for .project
and .settings, which are eclipse-specific configuration files.
Adds a failing unit test to show a problem caused by the update of jQuery which introduced a bug where the previous layout style will be amended rather than overwritten.
Refactors SC.RenderContext to simplify the API, introduce consistent naming and make it behave appropriately.  This should remove the guess work about whether a function is or is not supported by the context and make it easier to remember the names and parameters of each method.

- There are now 3 similar access methods:  attrs(), classes(), styles()
- There are now 3 similar add methods:  addAttr(), addClass(), addStyle()
- There are now 3 similar remove methods: removeAttr(), removeClass(), removeStyle()
- There are now 2 similar reset methods: resetClasses(), resetStyles()
- Fully backwards compatible.
- Duplicate and inconsistent method names have been deprecated:  css(), html(), classNames(), resetClassNames(), attr()
- Adds several Developer Warnings to aid developers in updating their code (in debug mode only as not to take up space in production).
- Removes some code duplication and simplifies the code.
Fixes bug noticed by updated jQuery.  The previous version of SC.RenderContext:addStyle() would replace styles, which was really only due to an undocumented behavior of jQuery, plus it is semantically incorrect for 'add' to replace.  The refactor of RenderContext makes the functions behave properly.
Updates all render context methods to use the updated API.  This should make it clearer that the context is not a jQuery object and shouldn't be used like one.
Fixes typo of missing '@' on endif, which would cause non-debug builds to become invalid.
Fixes improper use of execUnsafeLocalFunction polyfill so that jQuery tests work properly.
Makes invokeNext trigger the next run of the run loop if none is scheduled.   This makes invokeNext the appropriate method to use when needing the DOM to be up-to-date before running code against it.

Previously, invokeNext functions would not run until the next run loop occurred, which if there were no events or timers, might mean that the code won't run for a long time.  While invokeLast lets you put code at the end of the run loop, the DOM will not have yet been updated and invokeLater is risky to use at small intervals, because if the interval is too small, the invokeLater code will run in the current run of the run loop and again the DOM will not have been updated.  Instead, invokeNext now ensures that the run loop completes execution and schedules an immediate timeout in order to allow the browser to update the DOM.

This works with the timer additions to the run loop, so additional run loops only run once even if there is an invokeLater expiring at the same time as the invokeNext timeout triggers a new run loop.

- Includes unit test.
- Fixes bug in previous unit test that left a run loop unfinished.
Fixes CoreTest.Runner to start on the updated jQuery ready event.
Improves the documentation for invokeNext.
Makes the rendering of animation layouts asynchronous always to ensure that the current layout of the View gets rendered to the DOM.  If the current layout is not rendered, the animation layout will be all the DOM sees and thus it won't trigger an animation change.   This should make using SC.View:animate much easier, especially for new developers.

Also scrubs layout_style.js to remove a number of unused variables, support the above change and optimize the variable declarations.  This optimization dropped the minified file size from 9,322 bytes down to 8,914 bytes (408 bytes reduced).
Cleans whitespace.
Cleans whitespace.
Refactors transition and animation testing of SC.platform; adds SC.browser.cssPrefix, SC.browser.domPrefix and SC.browser.classPrefix; adds SC.browser. experimentalNameFor(), SC.browser. experimentalStyleNameFor() and SC.browser. experimentalCSSNameFor() methods; and adds SC.UNSUPPORTED constant.

There were many problems with the animation and transition tests that existed before.  There was no forward support so browsers, like the Firefox nightly that have dropped prefixes, would fail to identify as supporting transitions and transforms.  Also, animation event listeners were hard coded into RootResponder for webkit only.  Also the event names needed to be forward supported as well and because there is no consistency in the event naming, the real transition and animation events may not have been captured on certain browsers.

Now, SC.platform does quick and precise tests to determine the actual event names allowing the RootResponder to listen only to the properly named events rather than using a shotgun approach with a bunch of different browser prefixes.

To make the code forward compatible for when prefixes are dropped, SC.browser has three new support functions:  experimentalNameFor(), experimentalStyleNameFor(), experimentalCSSNameFor().  These functions return the proper name for experimental names for object classes & properties, DOM properties and CSS attributes, not by guessing, but by testing the standard name and then testing prefixed versions of the name if necessary.  This allows developers to avoid writing code like:  SC.browser.cssPrefix + "box-shadow black 0 1px 2px", which will fail on browsers that no longer need a prefix and instead use:  SC.browser.experimentalCSSNameFor('boxShadow'), which will return either "box-shadow", some browser prefix + "box-shadow" or SC.UNSUPPORTED (allowing you to do something else).

- The css prefix and dom prefix were calculated from the user agent, which duplicated work already done with more rigor in SC.browser.
- Fixes duplicate 'input' property in SC.platform.
- Deprecates SC.platform.cssPrefix and SC.platform.domCSSPrefix.
Updates test to use proper domPrefix value rather than the deprecated version.