Moving logic from ravenpy.utilities to other packages (as much as possible)

[cjauvin]

In order to remove heavy dependencies and further reduce the conceptual surface covered by RavenPy (its core mission, after all, is to be essentially a RV config generator, along with a Raven process launcher and manager), we (@cjauvin and @Zeitsperre) have discussed today the possibility of moving logic away from ravenpy.utilities as much as possible: some components (like geoserver) should maybe go back to RavenWPS, and some others into a new separate package, with a name like ~RavenGIS (from which RavenWPS would depend, but not RavenPy).

[Zeitsperre]

Moving GIS functions out of there would not only help set the scope of RavenPy, but would also make maintenance of the GIS dependencies much simpler to manage. It would also allow us to remove the GIS warnings from many modules. It wouldn't require much effort either (cookiecutter would do 90% of the work). Seems like a slam dunk.