HTML syntax part 2: mandatory <script></script> and optional <!-- HTML comments -->

The first two commits should be straightforward, first is renaming things, second is whitespace-only change.

Third commit:

- `build/grunt/docs.js` just better error message
- `gruntfile.js` some unrelated debugging comments, I really don't want a separate commit for that ;)
- `hsp/compiler/jsgenerator/index.js` and  `hsp/compiler/parser/hspblocks.pegjs` main changes here; I've decided to emit newlines from the parser side and just glue blocks together in js generator instead of joining them with `\r\n`, IMO this simplifies reasoning about the code and line mappings. The edge case I encountered with the old attitude was for instance was that
```
<template>
</template>
<template>
</template>
````
generated one newline between the templates in JS code (template + `\r\n` + template) while
```
<template>
</template>

<template>
</template>
```
generated *three* newlines between them (template + `\r\n` + one-line whitespace block + `\r\n` + template).

So, let each top-level statement care about its own whitespace from now on. `<script>` and `</script>` tags also emit a newline to keep the 1:1 line correspondence.

- `test/compiler/errtests.js` some files have lines shifted due to introduction of `<script>`, this accomodates for that
- `test/compiler/tests.js` template1 is now longer, so line map update was needed
- other files: just introducing `<script>` tag everywhere where needed

Fourth commit:

`hspblocks`, `syntaxTree` and `comment-toplevel1` are most interesting. Other files just change `<script>`-based comments to HTML-based ones.

I emit original comment content at parse time (just like it's done for comments in templates) and discard them at syntax tree build time (replacing with newlines so that line map algorithm doesn't need updates; we may improve that later).