Amp-bind: Rearrange grammar rules and regenerate parser

[kmh287]

• Modified the performance example to use different expressions per binding to circumvent the new caching strategy
• Updated the grammar in bind-expr-impl.jison to remove FALSE, TRUE, and NULL. Is there any reason to support these? They're not supported in js.
• Updated the grammar in bind-expr-impl.jison by rearranging the tokens. The parser checks every potential token against this list in order, and so I've arranged them to try to put the more likely ones first. e.g. a NAME is probably more likely to come up than the mod operator. That being said, this is just my guess and I'm open to suggestions.
• Regenerated bind-expr-impl.js based on the above changes. All changes in that file were made by jison, except changing the copyright date at the top.

With the changes to the performance HTML file and the parser, the time it takes Bind to parse bindings on performance.html decreased by 10% on my machine. (Chrome 56, CPU throttling at 10x, two different experiments with 10 tries each comparing master's bind-expr-impl.js to the one on this branch, web-worker experiment disabled)

/to @choumx, @jridgewell

[jridgewell]

What's this for?

[kmh287]

It's part of the autogenerated file. I'm not sure if they added this in the newest version of jison or if @choumx just removed it from previous versions.

EDIT: Judging from the CI error it's the latter. I'll remove it now.