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

Remove instrument_sensitivity if it exist. If it doesn't exist, then
an instrument_polynomial must describe the response, which is how the
Geomagnetism Program specifies an offset and gain response. We do not
attempt to remove any frequency-depenent response since these all seem
tailored to seismic data (e.g., no DC/zero-frequency response).

Added necessary check within FDSNSNCL.py to assign the sncl.channel as LF1,LF2,LFZ when X,Y,Z are requested by the user.

REsolved comments made by Josh. The rotation function is now sampling frequency agnostic, while also relying on the original stream created under get_timeseries.

Removed previous lines of code that checked metadata for Azimuth and Dip and replaced it with a new function that rotates the Stream object if channels X, Y, or Z, are requested and returns the appropriate channel after rotation.

Fix FilterAlgorithm.align_trace() method and unit tests

See merge request !336

The method FilterAlgorithm.align_trace() pre-processes the `trace.data` input
array for subsequent processing by FilterAlgorithm.firfilter() such that the
first input array element corresponds to a time step on which output samples
must fall (as defined in the dictionary `step`) minus half the fir window
width. In short, it ensures that output samples fall on desired time steps.

Prior to this fix, it only worked as intended when input trace's starttime fell
on an even time step. A bug became obvious when attempting to filter data from
non-Geomag stations that did not have nice time stamps. This fix addresses that
issue, and also ensures that `align_trace()` does what was claimed in its own
original docstrings, which is to handle trailing misalignments as well.

Note: one thing `align_trace()` does NOT do is ensure that all needed input
data are available to generate desired outputs. The user is responsible for
providing this, but can use the FilterAlgorithm.get_input_interal() method
to calculate the actual required input starttime and endtime. The method
`align_trace()` will trim or pad with NaNs only enough to align time stamps,
and may actually result in `firfilter()` output that are NaNs if the input
trace was not adequate.

Trying a better "rebase" (https://stackoverflow.com/a/71982894)

Changes to AdjustedAlgorithm and AdjustedMatrix classes (and unit tests)

See merge request !328

It was necessary to explicitly set inchannels and outchannels when
instantiating the AdjustedAlgorithm class in unit tests after other
changes in this MR were made to remove the hard-coded default
inchannels and outchannels.

- no longer forces default inchannels and outchannels, and lets the
  AdjustedMatrix.process() method "do the right thing" if neither is
  explicitly set by the user
- some mostly aesthetic changes that more cleanly separate the vector
  and scalar (F) adjustements
- modified AdjustedAlgorithm.can_produce_data():
  a. if any non-F inchannels cannot produce data, return False
  b. if F inchannel can produce data, return True as long as all
     non-F inchannels can also produce data
  c. if this is not desirable (e.g., you want to treat non-F and F
     channels independently), it is necessary to create two instances
     of AdjustedAlgorithm, one for non-F inchannels, and one for F.

- explicitly setting inchannels and outchannels is now optional,
  and default values are pulled from the input stream argument
  of AdjustedMatrix.process() method
- *if* non-F inchannels and outchannels are specified, they are
  checked for dimensional consistency with each other, and with
  self.matrix
- returns dimensionally consistent array of NaNs if there is any
  mismatch in inchannels, outchannels, or self.matrix
- raises exception only if all inchannels are not provided in
  the input stream
- requires F be specified in both inchannels and outchannels, or
  else it returns NaNs for F

This sounds a little complicated, and it is, but it was necessary
in order to allow the AdjustedMatrix class to adjust both vector
values (e.g., HEZ->XYZ), as well as scalar F values (e.g., pier
corrections). An argument could be made to separate these, but I
am not willing to do so at the moment.

Added several changes to allow for users to retrieve one minute and one hour...

See merge request !329

Resolved comments made by Josh. Added FilterApiQuery.py and renamed the Filter.py to filter.py for consistency.

Updated poetry lock file to contain updated version of gunicorn 23.0.0. The old version was a vulnerability.

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.

The hour data is still doing something wonky but I'm not sure why. The first hour returned has an additional 30 minutes.

Added severl changes to allow for users to retrieve one minute and one hour data from the avaiable one-second data via the FDSN client.

Replace pipes in metadatafactory w/ unions

See merge request !333

Update metadata factory with timeouts and docstrings + use timeouts in instrument calibrations

See merge request !332