RFC - 1.0 Version Support

We need to make a final decision on version support for FTG:R 1.0 (Beryllium).  Here is a plan that was put out on the developer's private board at the time of 0.2 (Helium) release:
![browser support](https://cloud.githubusercontent.com/assets/2197376/2711115/3abff2b2-c4ca-11e3-9d4a-ae8f0c2a82c5.png)
We've already decided per RFC #13 to discontinue support for 5.3 in version 1.0, however, I propose that the 0.4 idea be shut down.  It would be too hard to backport everything and put in itemOf() functions.  The new codebase is too dependent on the function_name()['foo'] syntax to release for PHP 5.3; in addition, 5.3 is shutting down this summer.  I propose we mark 0.3 as LTS and support it at least until July when 5.3 is officially not supported and we will make a decision from there.

Now onto browser support:
IE8 was used on 6.2% of computers during the month of March according to this website: http://gs.statcounter.com/#browser_version-ww-monthly-201403-201403-bar.  However, it was decided in private discussion to discontinue support for IE8 in 1.0 because of the variety of HTML5 effects that we want to portray.  Again, 0.3 LTS can be used for this purpose if sites want to support IE8.  If we are not supporting IE8, then it makes no sense to use jQuery 1.11, it makes more sense to update to the faster 2.1.  2.1 is a 12 KB reduction from 1.11, a 12.5% size reduction.  In addition, the 2.x branch will be supported for much longer than the 1.x branch, and testing showed no problems with the game.  I propose we move to the latest stable of jQuery 2.x, and give an option to revert to the latest stable of 1.x.  We will continue hosting them from Google, but I'd prefer to update the version numbers manually with a patch rather than trust Google with the latest version before we can test.  We can also put in a constant for backporting to jQuery 1.x, but that will be an "at your own risk" sort of thing.

If anyone has any commits related to this issue, please commit or open a pull request to the dev-browser_support branch so that we can approve everything in one pull request.  If you need to make a pull request, those pull requests should be regarding whether they are applicable to this RFC; disagreement with this RFC should not be reason for dismissal of a pull request to it.