Fix location for datasets with 'Y' instrument_id

[ngachung]

Clone of https://github.jpl.nasa.gov/Mass-Change/gmat-ingest/issues/337

[ngachung]

Currently, location functionality only works for spacecraft-specific datasets, because it assumes that instrument_id for the dataset is the same as for GNV1B datasets, which has 'C' or 'D' for instrument ID. So, if the dataset has 'Y' instrument_id, location fails to attached:
{
"detail": "instruments id "Y" not recognized (expected one of ['C', 'D'])"
}

[ngachung]

This change is not needed, at least for now: for Events, will have separate files for separate spacecrafts.
For other datasets with 'Y', an investigation is needed to determine on how to geolocate the data

[IrinaTkatcheva]

I will keep this ticket open as a reminder to review geolocation for datasets with Y spacecraft.

[IrinaTkatcheva]

According to Dave, geolocation for Y data should be in the middle between satellites. Simple linear interpolation for lat/lon is good enough. Pay attention to antimeridian (+/-180)