whitespace police raid
- add support for aliases for terminals (included test case to verify proper operation of this feature)

- when productions have aliases for any (non)terminals, we do not require anymore that the action code must use those aliases: it may chose to use the original (non)terminal identifiers instead.

- added a bit of documentation comment in the source code where action code is expanded for (non)terminals and aliases: as I went through this bit of code, I noticed another feature which was unknown to me before. Here's the comment chunk:

> Also note that each (non)terminal can also be uniquely addressed by [$@]\<nonterminal>\<N> where N is a number representing the number of this particular occurrence of the given (non)terminal.
>
> For example, given this (intentionally contrived) production:
>
>        elem[alias] elem[another_alias] another_elem[alias] elem[alias] another_elem[another_alias]
>
> all the items can be accessed as:
>
>        $1      $2              $3             $4      $5
>        $elem1  $elem2          $another_elem1 $elem3  $another_elem2
>        $elem   $elem2          $another_elem  $elem3  $another_elem2
>        $alias1 $another_alias1 $alias2        $alias3 $another_alias2
>        $alias  $another_alias  $alias2        $alias3 $another_alias2
>
> where each line above is equivalent to the top-most line. Note the numbers postfixed to both (non)terminal identifiers and aliases alike and also note `alias2` === `another_elem1`: the postfix numbering is independent.
update webpages: `make site`
updated gh-pages: `make deploy`
include the grammar production (rule) inside a comment with each action block for easier debugging. (Minifiers throw away such comments anyway, so it does not slow down production code in any way.)
add a comment for each lexer and parser ACTION block listing the start conditions + matching regular expression and the production (rule) respectively: these help a lot in analyzing/debugging generated grammars without any speed decrease as comments are quickly removed using any kind of JS minifier tool in production/releases.