convert to a common node/broswer compatibility practice

http://www.matteoagosti.com/blog/2013/02/24/writing-javascript-modules-for-both-browser-and-node/
drop inline-require.js and generate just the grammar js
serialize grammar in a more diff'able form

generate rules line by line
also, use ternary if  in serializePostprocessor and serializeSymbol
make Rule a full object factory and add State methods

move rule toString from State to Rule
rewrite State .consume as if-then to remove implicit order of eval
swap State .process arg order to match advanceTo arg order
add .advanceTo as a method on Paarser
inline setup func as part of Parser obj creation
as part of Parser init, convert raw grammar objects to Rules
renname token consumer methods

rename State .consume to .consumeTerminal and .consumeRule to
.consumeNonTerminal to reflect standard terminology
allow end user to name grammar

end user can name grammar when in used in the browser
update test/profile.js for new grammar/parser invocation
run tests from powershell

windows powershell script to accomplish the same as launch.sh
clean up code output, add in the "id" thing
documented the new API
reworked calculator example to work with the new API
Merge branch 'rwindelz-nearley-needs-more-objectness'
please keep custom scripts gitignore'd
removed an npm debug log
shinier tests and better documentation
1.0.0 -- backward-incompatible changes -> semvar
trailing newlines