This was causing issues with the Controller, which always passes `sncl_mode`, even if it is None.

- MiniSeedInputClient expects a stream as input, not a trace
  (like RawInputClient), and unit tests were designed around this;
  I reverted _put_channel() to its original design, which sends an
  entire stream instead of one trace at a time.
- I forgot to include a tiny change to RawInputClient_test that was
  part of the original (abandoned) MR
- I also made the read client timeout configurable

- handle intervals other than 1s and 1m properly

    - configurable scale_factor and float vs. int conversion logic
    - configurable sncl_mode for different channel mapping
    - multiple read ports allowed for fail-over logic
    - generally more (if not perfectly) compatible with MiniSeedFactory

- configurable scale_factor and float vs. int conversion logic
- configurable sncl_mode for different channel mapping
- multiple read ports allowed for fail-over logic
- configurable write_encoding for setting miniseed data type
- generally more (if not perfectly) compatible with EdgeFactory

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

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 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.

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.

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.

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.

Reviewed comments made by Josh and removed debugging print statements and changed _get_channel_start to get_channel_start within SNCL.py and any other script which references this function.

Fixed the bugs cuasing interval to be defined as none. This required changes to the FDSNFactory.py after fixing this another bug was found in IAGAWriter2002.py, This was also fixed. The change made to the test_metadate.py script was something that Nich told me about that hasnt been merged in yet. Happy to take it out if need be but I left it in for the time being.

Added the @interval property to store the data interval based on the channel start for Variometers. Hoping this fixes the issues you saw in mage1. I also added an FDSNSNCL_test.py script.