Optimize JS, move JS ResLoad module, bump to 0.3.3

This commit introduces a major change in the structure of js/ext.CommunityTwitter.updatecount.js and
a minor change in the code for CommunityTwitter_body.php. The JS code for updating the characters
remaining counter proved to be a source of lag on mobile devices such as the fifth-generation iPod
Touch, with much greater lag time expected for devices which are less powerful. The source of this
lag was identified to be the relatively-expensive recursion of document.getElementById three times
per character input, once for the textarea element to grab the number of characters used, the strong
element for the counter output, and the input element for disabling/re-enabling the "Tweet" button.
Two methods were used to optimize the JS, implemented in chronological order: (1) A global variable,
ctStatusForm, was defined to get the form element for the tweet box using document.getElementById.
Using ctStatusForm.getElementsByTagName, the user's JavaScript engine only needed to search within
just the form element to get the three Element objects every time a character was input,
significantly reducing lag time. (2) A self-invoked, anonymous function now contains the 4 element-
getting variables, as well as the attachment of the counter update function to
ctStatusTextarea.onkeyup. This effectively creates a closure, eliminating the need for true global
variables while also eliminating the need to re-get the elements every time a character is input.
This makes the update counter's resource expense negligible, reducing it to minor on-load lag.
As for the PHP code, the loading of the JavaScript ResourceLoader module was moved to inside the
if-else branch containing the status update box so that it is only loaded when the status update box
is loaded. Finally, the version was bumped to 0.3.3 since the restructuring of the JS code is major.

Change-Id: I0f96a57c63553ca1618d75bca2bb67187cdde7e6