dataset selection should interact with geometry and calculation sections

[bekozi]

who: @bekozi, NCPP, Seth McGinnis

When a geometry is selected, only datasets that have a spatial overlap with the ROI should be available. The same should be true in regards to the dataset selection. This will require:

1. Moving geometry storage into a database and connect this with the API Luca built to access the geometry JSON. I think they can sit in the same database as the datasets.
2. Add options for spatial-like queries to the database. I don't think we will have to move to Postgres as the spatial operations will be comparing against bounding boxes which can be constructed and used in intersects operations quickly.

When a calculation is selected/enabled:

1. Describe how a particular temporal output frequency will modify the time coordinates
2. Remove unreasonable frequencies (i.e. day frequency for daily datasets)