Test Cesium under node

Now that we ship an official Cesium node module, and the non-webgl parts are actually supposed to work under node, we should include node testing as part of the CI and release processes. I think we can leverage all of our existing jasmine tests and run them under node unchanged (of course many will fail), and then the hard part will be to go in and make them work (where it makes sense) or add them to a "noNode" category. In the short term, we might just be able to add a smokescreen test to ensure the module isn't every completely broken.
- [x] Smoke screen test for module to make sure it loads without issue.
- [ ] Make all current non-webgl tests runnable under node via jasmine.
- [ ] Fix any broken tests or if needed add them to the `noNode` category.

Start by locating the existing Jasmine tests, the Cesium Node module, and the completed module smoke test. Run the current tests under Node to identify non-WebGL failures. Done means current non-WebGL tests run through Jasmine under Node, with broken tests fixed or placed in the noNode category, and Node testing included in CI and release processes.

Written by the indexing model from the issue text.