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.