Migrate GeoAPI off Dojo

[james-rae]

Once the ESRI API is finished migrating off of Dojo (likely v4.17), attempt the following.

• Rip out all the Dojo loading stuff.
• Use the ESRI API that will be published on npm as a project dependency.
• Convert all uses of EsriBundle to now just import classes from the npm library
• Move the GeoAPI code inside the ramp-core package. This will improve:
  • ease of using types and interfaces in the core
  • will vastly improve the ability to step through GeoAPI code when debugging
  • can hot-reload when changing GeoAPI code

[james-rae]

Another consideration: if GeoAPI is moved inside the ramp-core package, we can investigate ways of leveraging the RAMP event bus and thus getting rid of the GeoAPI event system (though it is pretty amazing).

This is a bit of a trick, as the GeoAPI exists as a stand alone entity, and the RAMP event bus exists on RAMP Instances. So possibly we need to register RAMP Instances with GeoAPI so it can pepper events to all valid instances. Alternately we can entertain spinning up a GeoAPI for each instance; since we would no longer be doing a Dojo load, the performance hit is more in memory space.

TBD....