Previously, the `color-touching-tests.sb2` test "touches a color that
doesn't actually exist right now" would use a sprite with ghost 50,
blended against another sprite, to create the color that "doesn't
actually exist" when the query sprite is skipped. Unfortunately the
blend result was near a bit-boundary and, depending on the specific
hardware used, that test could fail on the GPU. When the renderer uses
the CPU path this test works fine, though, so the existing problem went
unnoticed.
To fix the problem I changed the project to use ghost 30 instead, which
results in a color that is less near a bit boundary and is therefore
less likely to fail on specific hardware.
As an example of what was happening: the `touching color` block was
checking for `RGB(127,101,216)` with a mask of `RGB(0xF8,0xF8,0xF0)`. On
the CPU it would find `RGB(120,99,215)`, which is in range, but on some
GPUs the closest color it could find was `RGB(119,98,215)` which
mismatches on all four of the least significant bits -- one of which is
enabled in the mask.
* Quick example of a collision test integration test
* Add a test for ghost and hidden sprites
* enable scratch/es6 which then had my lint error for `(param) => {}` arrows
* cleanup npm test command
* an a was an an but should have been an a
* 2space tabs for the html doc
* Add some comments in the integration index html
* Add a few more comments about intentionally leaking variables into the global scope
* add some more comments for the integration helper and add a timeout
* 4 space tabs are actually correct
* adding even more comments and improving readability a little
* fix lint no-shadow rule
* fix indentation on comment
