Separate the view-model into its own module.

[marshallswain]

The can.Map that makes up the viewModel could be used on its own, so it doesn't necessarily need to be used as a component. I can set it up so that the viewModel is the default export, so doing

import geolocation from 'geo-location';

would let you add it to an existing Map, but would also register the can.Component to be used in templates with the current import API:

<can-import from="geo-location"/>
<geo-location ... />