Updated the filter endpoint to not allow for the output sampling period to be none. If it is left empty an error code wil prompt you to provide an appropriate sampling period. This involved adding some logic to a few of the test and a couple logger warming that would skip trying to determine wehter the number of smaple reqeusted ignores the sample request limit.

Reverted test to allow strings for specifc parmaters. I believe I grabbed an old version of DataAPIQuery that caused the test to fail before. Things should now be up to date.

Removed the default auto from input sampling period. Added descriptor to swagger saying that  will generate correct sampling period needed to find the output_sampling_period.

Created a fresh branch to commit changes to files for adding recursive logic, also adjusted current tests to accomdate these changes. I added a new test FDSNFactory_test as well as a mock miniseed client called mseed_FDSN_test_client which is simply the same as mseed_test_client but adapted to use the FDSNSNCL.

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.

Commented out FDSNFactory_Test.py for the time being. Updated poetry and added a new script Filter.py to handle the FilterDateApiQuery class that is used for the filter algorithm web service.

I have added a new class to the DataApiQuery.py that is used within algorithms.py to provide an input and output sample interval option for users.

I have added a new class to the DataApiQuery.py that is used within algorithms.py to provide an input and output sample interval option for users.

I cahnged the call from IRISFactory to FDSNFactory in data.py, updated the validator in DataAPIQuery.py to accept Variometer IDs, added a new file called variometers.py so that the ASL_Observatory_index can be used by the webservice, and this includes a change to app.py where I added a router to the new variometers.py script. I opted to not change any of the file names currently, but will give this some more thought. I wanted to commit these chagnes soon so that Nick can begin working on the front end.

We can't totally obscure things and fairly call this an "open" api.
However, if we prefer to limit experimentation by novice developers,
it seems prudent to at least partially obscure some options in the
user-friendly Swagger for our api. This seemed especially important
for the data_host option, which could be susceptible to abuse. So,
all models/schemas are published via `ws/openapi.json`, but only
"default" options are displayed on the Swagger page's "Try it out"
section.

Allows the user to specify an alternate host to pull time series
data from via the URL. This is mostly useful for using the data
web service to test different verified data sources. It is not
really a "public" feature, and we might consider how to restrict
its deployment to non-public servers only.

update get_data's usage of get_data_factory