Improve context version handling in test harness

Harness now shows clearly if the selected version of WebGL is not
supported, and test links point to the test with the right WebGL version
selected, so results are consistent whether you run the test with the
button or follow the link.
One comment: perhaps this could be more descriptive ("does not appear to support WebGL 2"), depending on what the user's intent was?