Fusera and sracp completely updated

Changelog

speed increases in sracp
new help interface for both fusera and sracp
better error messages
faster startup time for fusera
fusera can be limited to certain filetypes

v0.0.6: Merge pull request #92 from mitre/fix-batch

Correct comparison of location prefix

v0.0.5: Merge pull request #90 from mitre/batch-retry

Changelog

This release adds a retry request to batch calls that get an HTTP error message from the API. It also improves the printout when a batch does fail by including the number of accessions that failed in that batch and a list of those accessions. Finally, a small issue with the help was found where it was showing the defaults for batches being 0. They are actually 10 for GCP and 50 for AWS, and so now the help says as such.

v0.0.4: Merge pull request #76 from mitre/sracp-like-cp

Changelog

This release updates sracp. Now, sracp will carry on if the folders already exist where sracp will be putting the copied files. It also will copy over any existing files similar to the cp tool. Finally, sracp will attempt to detect if it is running out of disk space and will skip files that would exceed the available disk space on the machine.

v0.0.3: Merge pull request #75 from mitre/batch-acc-requests

Changelog

Fusera now provides an error.log file inside the folders for accessions that encounter errors. This way, a user can read the error.log file to find out more about why that accession failed. It can also be handy for scripting, as its shear existence indicates that something went wrong inside that folder, so a script might want to skip it or take note of that.
Fusera now batches requests to conform to the Name Resolver API's limits on how many accessions can be requested per request.
Finally, a small bug was fixed where the expiration date for files weren't getting updated with the signed urls so after a signed url would expire, fusera would always request a new signed url on every read. This behavior was undesired so it was fixed.

v0.0.2: Merge pull request #71 from mitre/resolve-gcp-loc

CHANGELOG

Fusera and sracp can now resolve locations on Google's Cloud Platform. Just leave the location flag (-loc) blank and fusera will attempt to use AWS and then Google endpoints to determine what cloud provider and region it is operating in.
This release also opens both fusera and sracp up to using the ftp-ncbi region, although using them with an ftp protocol has not been tested. Some functionality seems to exist, but more investigation is needed.
Finally, some improvements were made to how help is printed, such as ensuring the help message is displayed when running fusera without any arguments. It seems that adding subcommands (mount and unmount) caused this to go away, but it's back now!

v0.0.1: Merge pull request #68 from mitre/cfg-endpoint

CHANGELOG
Sracp now comes with a file types or “only” flag to download only the listed file types for all accessions listed.
Fusera now comes with a configurable endpoint for the Name Resolver API, only to be used in the event that fusera needs to change which version of the Name Resolver API it is using. This has already proved useful, as the current default endpoint for fusera contains a bug. For now, the last known working endpoint is names/names.cgi.

Beta

Merge pull request #65 from mitre/fix-nr-status-checks

Construct printout of failed accessions & fail when no accesions to m…