Shotdata model should follow the community standard format

[frigusgulo]

At this point we have been storing data into the GARPOS defined seafloor acoustic data format [https://github.com/s-watanabe-jhod/garpos].

For longer term storage and ease of use with API's it could be more prudent to store this data in the format outlined by the Seafloor Geodesy Standardization Task Force. This dataframe model and TileDB schema would allow us to create an API that would be more generalizable to GNATTs and seems to be more widely used.

The only real changes would be that parsing SV2/3 files that generate this data would need to be done with the site meta data:

shotData_df = dfop00_to_shotdata(novatel_file,site_metadata)

as opposed to the current approach:

shotData_df = dfop00_to_shotdata(novatel_file)

TODO:

1. Create community standard format TileDB array and dataframe model schemas
2. Move Site and Vessel metadata schemas back to this repo
3. Incorporate metadata into the processing pipeline
   3.1 Avoid redundant metadata downloads
   3.2 Store Meta-data catalog in a master file
   3.3 load meta-data catalog into datahandler object