Fix Inconsistencies for Location

[mikebotts]

The data structure and use of definition attributes are inconsistent for different sensors. In some cases, there is only the sensorLocation observable with no latitude, longitude, or altitude observables, while in other cases, there are 4 observables for location, lat, lon, alt.

The issue seems to stem from a few reasons:
(1) many of the location outputs are the result of using GeoPosHelper in the drivers. The code in GeoPosHelper does not add definition attributes for latitude, longitude, and altitude, thus they get left out of being observables within the Capabilities doc. This may be OK from the standpoint of SOS, but the lack of definitions for Scalars goes against SWE Common Data rules. It also makes it hard to assign, say, altitude to a chart styler without special processing in the data receiver. NOTE: this is also the case for Quaternion vectors, etc. We need discussion on this to determine best approach to control what observables are exposed while complying with the SWE Common Data standard.

(2) The drivers supported through the Android OSH version have a different behavior for location. The later versions (for Android phones, e.g.) tend to include location, longitude, latitude, and altitude, while the newer versions include only location.