124 continued - exported variables updated for consistency

See merge request !350

Use Project's Container Registry

Closes #124

See merge request !348

updated where image is published

See merge request !347

Hotfix for Windows OS support

See merge request !345

Updated the controller.py file to incoorporate the FDSNFactory for command line arguments.

See merge request !334

Upgraded FastAPI and do not seem to be experiencing all the same bugs that were present last time we upgraded fastapi. This also upgraded Starlette to version 0.40.0 which was necessary to build docker image.

Added a warning message for FDSNFactory in the case a user is requesting data from the command line and assigns innaporopriate arguments.

Update Release Tag

See merge request !343

Network Parameter Addition

See merge request !342

Added a network paramter to all list of Observatories and Variometers. I made this a non optional paramter within Observatory.py.

Fix _post_process() in FDSNFactory

See merge request !341

The FDSNFactory was not working with input streams that contained multiple
segments. This was because FDSNFactory wasn't doing the full "_post_process"
like, for example, EdgeFactory. More specifically, FDSNFactory's `_post_process()`
method did not convert masked arrays (which is how obspy prefers to deal with
gappy data) into regular numpy arrays with NaNs for missing data, as expected
in all geomag-algorithms code.

This became quickly obvious once some of the less stable ASL variometers
were processed, like US-EYMN. This fix should allow us to now pull and plot
EYMN, DGMT, and other stations that were not working with the previous
release of FDSNFactory.

Adding a few changes to FDSNFActory regarding the FDSNNoDataException. I also...

See merge request !340

Updated data_test.py to not retrieve FilterApiQuery from DataApiQuery. Honestly not sure how these are just now causing issues when all my previous commits have contained this code.

I removed an unecessary call to FilterApiQuery from within Data.py. I also added validation to the FilterApiQuery.py. Rather than using super I opted to add the validation to this file beacuse sampling_period was ignored from the base class i.e. DataApiQuery and this is why the REQUEST_LIMIT was being ignored.

Adding a few changes to FDSNFActory regarding the FDSNNoDataException. I also created a private function to contain the logic that removes sensitivity/response info for traces. I added all avaiable stations that transmit geomgagnetic data for networks, IU, N4, and US to the VariometerMetadata.py module.

204 Error Exception Handling

See merge request !339

Function get_nearest_time() behaves as expected now

See merge request !338

The previous unit test relied on broken behavior of get_nearest_time()
to pass. With get_nearest_time() fixed, the unit test needed to be
updated accordingly.

A FilterAlgorith.py module function get_nearest_time() is supposed to return
the nearest *allowed* time for a given filter "step". This worked fine with
steps for second and minute data, whose allowed times are the tops of seconds
and minutes. However, for hourly (and daily, and any "average" type step),
things failed since the allowed times are the center of the interval (for
example, for hourly data, which is the average of all minute samples from
00 to 59, the the allowed time is 29:30).

One consequence was that if a user specified an interval with a start and
end time that did not encompass a given hour's allowed center time (e.g.,
start=AA:29:31, end=BB:29:29), the algorithm would still return a sample
for time BB:29:30. More generally, requests for average type data would
include an extra sample.

In this fixed version, if start=AA:29:31, and end=BB:29:29, nothing is
returned, as intended (and as always worked for non-average type steps).
Furthermoref start=AA:29:30, and end=BB:29:29, a sample for hour AA is
generated; if start=AA:29:31, and end=BB:29:30, a sample for hour BB is
generated, and if start=AA:29:30, and end=BB:29:30, samples for both AA
and BB are generated, all as intended.

Remove Instrument Sensitivity/Response

See merge request !337

Added previous changes Josh made regarding the removal of the instruments response/sensitivity. I also added some default innit function incase the user wants to override this logic as requested in the original issue.

 Added logic to determine when to use the remove_sensitivity or remove_response function on trace objects. I alsoadded a remove_sensitivity flag to the __init__ function so that a user can override the default value of None fo instances where they want to use a specifc function and ignore the default logic.

FDSN 3D Rotation

See merge request !335