Pipeline updates

See merge request !188

Add absolutes

See merge request !189

Changed starttime/endtime to be defined by first absolutes reading starttime and last absolutes reading(last commit was supposed to include this but did not)

 Broke up code into smaller functions, changed starttime/endtime to be defined by first absolutes reading starttime and last absolutes reading endtime

Set proper timestamps in residual calculated absolutes

Closes #75

See merge request !191

Pyup.io's "safety" check failed on packages lxml, mako, and dparse.
None of these were explicit in our pyproject.toml file, but I modified
the entry to alembic, which was the package that required mako, then
ran poetry update to update the poetry.lock file.

To be honest, I'm not sure changing pyproject.toml file was needed
at all. I still don't fully understand how poetry works I guess. But,
everthing is "safe" now, and this merge request should now make it
through the CICD pipeline without further issue (fingers crossed).

The calculation of scale_value in geomagio.residual.calculate() is not
quite correct, but that needs to be addressed in a separate commit and
merge request. I'm reverting the recent change here so that we don't
break the tests.

Fixes #75

When geomagio.residual.calculate() is called with adjust_reference set equal
to True, the start/end timestamps now both reflect the time of the first absolute
measurement (i.e., West Down). This is consistent with the residual absolute
spreadsheet calculations.

Addresses issue #73 (residual spreadsheet time parsing)

See merge request !190

Switch get_previous_interval precision to milliseconds to match Edge

See merge request !187

update interval no longer shrinks with recursion

See merge request !186

Previously, the endtime-starttime interval being processed by the
`run_as_update` method would shrink by 1 (second) with each recursion.
This ultimately broke `run_as_update` when processing anything other
than 1-second data, but it wasn't obvious because we rarely had to
actually recurse. There is a little trickery now to ensure that user-
provided starttime and endtime are inclusive of the full first
(most recent) update interval, while subsequent, calculated, endtimes
are set equal to the prior starttime minus specified output_interval
(e.g., 'second', 'minute', etc.).

Parse data type in imfv122 files

See merge request !184

Attempt StringIO after failed BytesIO file read

See merge request !183

Gitlab 15 requires slightly different configuration to generate
Cobertura coverage reports. See:

https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportscoverage_report

Trying to dislodge a plugged pipeline in Gitlab

It turns out that none of the factories currently being used in
production expects bytes as input, and in fact, Util.read_url()
converts everthing to a string anyway, so a BYTES-oriented input
would couldn't not possibly be working. So, just remove all use
of BYTESIO, and instead use only STRINGIO.

It worked when a URL template was used, but not if a
single simple filename was passed

This is a bandaid to allow the `--input-url` option to be used to
read in single files. It adds zero functionality beyond what already
existed when the `--input-file` option was used.