update the creation of torqueScript html documentation via doxygen.
* updates to consoleDoc.cc
  *  output global script functions as "groups" instead of a "namespace".
  * this helps create an organization that isn't hacking the "namespace" C++ concept
* a new doxygen "layout" file
  * uses "groups" instead of "namespace" to get global functions organized well
  * for classes, uses the term "methods" and "fields" in place of "public attributes" and other default C++ what-not
* a new css files.
  * based on doxygen default but with much less bold text. :)
  * keeps all the unnecessary configuration in tact.  it doesn't hurt and it will be easier to diff with future doxygen defaults
in the docs, all parameters should be on one line like so:
   string Vector2Direction ( F32 angle, F32 magnitude )
documentation upgrade and cleanup
 * support torque2D doxygen
 * support for torqueScript doxygen on the code base (not by dumping symbols with a script)

moved support files (css, menu layout, footer/header) to a config dir
moved config files (run doxygen for engine or script) into config dir
some updates to doxygen config files.  getting closer to a system that documents torque2D with tags.  Then documents TorqueScript as a separate doc with links into the torque2D docs.  Before there was a concept for ConsoleFunctions and now there is a decent concept for ConsoleMethods as well.  Note that doxygen is unhappy with this idea as it was not designed for this.   So I'm trying to keep it as simple as possible while still working (frankly tricking Doxygen).
example of a few new concepts for documenting the engine and torqueScript.
Vector2_ScriptBinding.h: example of converting ConsoleFunctions
   * put @addgroup doxygen comments at top and bottom
   * convert ConsoleFunction to ConsoleFunctionWithDocs
   * change return type from S32 to ConsoleInt, for instance
   * move string-based comments to regular comments above the function instead

Simbase*: example of creating a scriptBinding file when there was none
   * pulled the ConsoleFunctions out of SimBase.cc and into SimBase_ScriptBinding.h
   * Added #include "SimBase_ScriptBinding.h" to Simbase.cc
   * Updated SimBase_ScriptBinding.h just like Vector2_ScriptBinding.h example
   * Added new file to VS2012.  Remember to do this for all compilers! (which I did not do for this check in)

Trigger_ScriptBinding.h: updated ConsoleMethods (class functions)
   * (no need to put @addgroup like with ConsoleFunctions)
   * put ConsoleMethodBeginWithDocs(Trigger) at the top of the file
   * put ConsoleMethodEndWithDocs(Trigger) at the bottom of the file
   * convert each ConsoleMethod to ConsoleMethodWithDocs
   * just like with ConsoleFunctions, move the comments and change the return type

may rearrange all this so I want a checkpoint via a commit.
moving TS functions from Doxygen "groups" to pseudo-namespaces.  This is an attempt to re-use the least number of concepts and we need namespaces.  Functions may have worked in a group but classes will not.  the reason is that the same class name will be seen in the engine via the tag file and confuse things.

also for engine docs, override a few "function-like macros" from the engine which heartily confuse doxygen.  (a semi-colon on the end of macro calls would probably work but that's a lot of files to touch)
Added a couple of comments to doxygen config for TS.  no biggie.
re-instated the layout file for torqueScript docs
several subtle changes such as adding collapsible diagrams to the t2d docs
changed ConsoleMethodEndWithDocs to ConsoleMethod[Group]EndWithDocs
tried a little trick to pull as much "old" Console function/method docs over as possible.  Seems to work pretty well.
change the name of output directories to be more useful when pushed to gh-pages.
new ReadMe for documentation.
Using doxygen "groups" or "modules" as a major factor in keeping the documentation (reference material and all) with the source.
- specifically, check the TAML Reference module and the Module Manager module for the engine.

To do this:
First the reference material from github wiki is brought over as a *.dox file.  doxygen understands markdown
95% well so not many tweaks are required.  By usingn a .dox file, the large reference is kept together and not
injected within a specific class.  Using the .dox is fairly standard practice.

The reference doc is placed in the dir that most closely represents it, such as module/module.dox or persistence/taml/taml.dox.

Classes in the module add themselves to their respective module with "/// @ingroup TAMLGroup" in the class header.

Now the markdown reference is inserted as a "module" and has references to all classes that are involved.

note: because the "modules" page in the output had lots of little groups, (such as dglThis and dglThat), I've also been pushing these groups into super groups to keep it organized (such as dglGroup which now wraps dglThis and dglThat).
checking in comment.rb temporarily for sake-keeping.  it is a script that can convert a scriptBinding.h file to the proposed doxygen format.  That is, it can convert ConsoleFunction, etc., with string comments to ConsoleFunctionWithDocs, etc., with doxygen comments.
Make a TorqueScript Reference in XML.  (Currently under 3MB which is nice.  The T2D XML comes in around 70MB already).
for doxygen
 * replaced the css file with an "extra css" file as doxygen suggests
 * updated simBase functions (scheduling and object functions) to be the reference for other docs
 * copied description of functions from ts to c++.  this doubles them but it seems the best (easy) way.
 * came up with a doxygen "alias" called @boundto to bind TS functions to engine functions in docs
Vector2_ScriptBinding.h:
Have to avoid the word "Vector" because doxygen sees the capital letter and links it to a class named Vector if it exists.  Must use lower-case "vector" or "%vector" to avoid that with doxygen.

Trigger_ScriptBinding.h & console.h & TorqueScriptReference.cfg
Added a "superclass" to the ConsoleMethodGroup* functions so Trigger can lead you to SceneObject where more functions reside and so on.
rolling back consoleDoc.cc as it was before the doc upgrade project.
Torsion will expect this older format (not that the code is ready to output in this format yet but might as well keep it clean)
changes weren't going to be used anyway.
Trying a different tact for producing TS docs.  This commit no longer links to the T2D docs which frees us from a few issues:

* using "groups" now instead of namespaces.  cleaner docs
* special groups for Data Types (string, Vector2) and Operators (SPC), as examples
* links to "Vector2" and "SPC" for instance, now point to Vector2 inside this doc.

Note that a pseudo-code scriptBinding.h file was created to contain the data types and operators.  This is the biggest "trick" but it does have benefits.  On the other hand, borderline tricks from before have been removed.
remove timestamps from footer.  this caused every run to produce a slightly different page for ever page: murder on version control.
Merge branch 'development' into torqueScriptDocs