Bypass geonode

[brucecrevensten]

This is ready for testing and perhaps even merging after some good fiddling! Things to test & review include:

• Does this work with all 3 maps and tours?
• Does this work when we do a grunt build and do a "production" deploy?
• Is the way the code is refactored to encompass the data we previously stored in GeoNode OK for the time being? It's not perfect and can be improved!

---

This change is 

[brucecrevensten]

It's worth pointing out here, there's a few more steps that can (should) be taken after this is merged, stable and deployed -- will sketch these in tickets when this work has been reviewed somewhat, but here's the roadmap:

1. Once production seems stable, we need to then migrate our data / layers directly into a new GeoServer instance (can use GeoServer 2.11 if possible, or 2.9?). We can create a Workspace for each map, to keep the namespaces for layers clean (can also keep shared layers in a default or shared workspace). We'd then need to update the source code to correctly reference the new layers, which may have different names (for sure, none should use the geonode: workspace prefix).
2. Redeploy production services to remove GeoNode and only have a GeoServer instance (+ our simple HTML bucket).
3. Deprecate/decommission the vagrant-geonode repository after verifying that there isn't anything there that should be moved elsewhere.