Updated several dependencies. Corrected USAGE.md. Fixed "blink" due to render order when rendering nodes

[aSqrd-eSqrd]

I updated several dependencies. In particular three and tween. I nudged tween.js up trying to get a version that contained a memory usage improvement, but the GIT version tags don't line up with the NPM versions so I'm not sure I actually got the improved memory usage.

I fixed a weird "blink" I had introduced when I added the shape code back in. The "blink" was that for a moment you could see the unlaunched particles and ends of the connection lines inside the node borders before the inner circle and any shape/icon rendered. It was because I was using renderOrder to correct for simply adding the meshes to the node's meshes in the proper order, see nodeViewStandard

WARNING: The following information is NOT an issue with vizceral, vizceral-react, or vizceral-example. It is with @tweenjs/tween.js, but I provide this information so hopefully other users don't lose half a day trying to figure out what broke their vizceral setup.

There is some strange bug in tween that causes either the traffic graphs to not display when you try to drill to a node (occurs with tween NPM v16.8.1 and v16.8.2) and I guess a different bug in tween (NPM) versions 16.9.0 and up. There is some strange prototype or method leak that causes three.js to get just a few of prototypes/methods from tween as attributes on objects. In vizceral, I tried three v0.96.0, v0.98.0, and v0.106.2 and if the tween version was 16.9.0 or higher the prototype/attribute thing happened regardless of the three version, and if the tween was v16.8.1 or v16.8.2 there were no errors or warnings but nothing was displayed when you drilled into a node.... so heads up on this. If you want to see this weird thing just update the @tweenjs/tween.js in vizceral and vizceral-example and after doing the npm link commands so you'll use your local vizceral, vizceral-react, vizceral-example together you just run npm run dev in vizceral-example.