gl-shader unlock

[dy]

We have to unbind gl-vao's in order to avoid warnings in console, which was the issue preventing from bumping gl-shader version. Still have to figure out why it happens so with unbound gl-vao, but here it is must-do patch.

TODO:

• gl-mesh3d gl-shader can be unlocked gl-vis/gl-mesh3d@894b143
• gl-error3d gl-shader can be unlocked as well gl-vis/gl-error3d@5abf599
• gl-shader direct dependency can be removed from plotly at all, there is no direct use of it Lock gl-shader to 4.2.0 plotly/plotly.js#931
• resolve unbound gl-vao issue https://gist.github.com/dfcreative/80153fb7be5b2fd486a6c78e7bdc0f1b

Supercedes #10

@etpinard I can do patches to according repos to unlock gl-shader version

[dy]

Ok, seems that it breaks some plotly tests. Still have to figure out the reason.

[dy]

False triggering, tests pass successfully. @etpinard may I ask you to check once you have a minute?

[etpinard]

Sure. But, that won't happen until 1.28.0 is out.

[jwerle]

excited to see this happen

[dy]

@etpinard should we proceed with that?

[etpinard]

@dfcreative see https://github.com/plotly/plotly.js/compare/unlock-gl-shader

This patch here along with gl-vis/gl-error3d#4 and gl-vis/gl-mesh3d#12 generate a few diffs in our image tests:

Most notably gl3d_log-axis, which is missing a trace:

compared to

on master (see http://rickyreusser.com/plotly-mock-viewer/#gl3d_log-axis)

[dy]

Since all tests are passing at plotly/plotly.js#2293, merging.