This eliminates the use of os.fork that could potentially cause a race
with threads and definitely genrates a DeprecatinWarning in Python 3.12.
How are we using threads? That's a mystery! Maybe multiprocessing.Queue?

One of the tests relies on there being a file we cannot update the update time on, which doesn't work as root.

Don't move empty files into place if a lock attempt raises an exception

https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/479

Attempted workaround for https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/479

Fixes warnings in output of test-example

https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/435

https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/435

Handles case where a user specifies a custom URL of something like
http://foo.com/ancillary which would expand to something like
http://foo.com/ancillary2024-08-05-file.data

https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/468

This reverts commit b63df565.

Avoids using the version in ShellB3, which isn't what we want (And is
busted as a bonus)

See #13 for details (Also tracking ticket at https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/402 )

A few tests had to change because error output no longer include "File
not found" in the output.

It was always broken, it just happened to work by chance. It
inexplicably passed a DownloadStatistics into the field where the file
object should be. We only got away with it because the failure happened
before the file was accessed. However, that's no longer going to be true
in a world where we hand the work off to curl.

Was testing the wrong variable for None-ness. The returned file from
atomic.__enter__() will be None if the file already exists, not the
atomic itself.

Slightly simplifies code, eliminating piles of calls to assertMockFile
and assertNoMockFile. Also will detect spuriously created files I didn't
think to explicitly test for with assertNoMockFile.

Chains Downloaders, allowing different data sets to fulfill a requirement.

fatal is an undocumented alias for critical

Ensure some code examples are flagged as ``code``

An example from a previous parameter was erroneously duplicated into the
next parameter

Likely typo. We have no guarantee we can write in the parent of the
temporal directory.