Better logs when accessing large files from S3

[adamnovak]

This should fix #4867 by changing the logging and exception handling around bucket location finding.

We now announce finding the location at the same log level as failing to find it (DEBUG), and leave reporting at higher levels up to the caller. Most of the callers seem to have fallback approaches to use when a bucket location isn't available, and so don't have to log anything at a higher level.

Also, to keep the user from getting bored during file imports, I am logging them at INFO:

[2024-05-23T16:30:15-0400] [MainThread] [I] [toil.jobStores.abstractJobStore] Importing input s3://human-pangenomics/NHGRI_UCSC_panel/HG002/hpp_HG002_NA24385_son_v1/PacBio_HiFi/20kb/m64011_190901_095311.Q20.fastq...

Changelog Entry

To be copied to the draft changelog by merger:

• Toil now announces imports at INFO level so it looks to be doing something
• Toil no longer complains as loudly when it tries and fails to ask AWS for bucket locations

Reviewer Checklist

• [ ] Make sure it is coming from issues/XXXX-fix-the-thing in the Toil repo, or from an external repo.
  • [ ] If it is coming from an external repo, make sure to pull it in for CI with:

    contrib/admin/test-pr otheruser theirbranchname issues/XXXX-fix-the-thing

  • [ ] If there is no associated issue, create one.
  • [ ] Read through the code changes. Make sure that it doesn't have:
  • [ ] Addition of trailing whitespace.
  • [ ] New variable or member names in camelCase that want to be in snake_case.
  • [ ] New functions without type hints.
  • [ ] New functions or classes without informative docstrings.
  • [ ] Changes to semantics not reflected in the relevant docstrings.
  • [ ] New or changed command line options for Toil workflows that are not reflected in docs/running/{cliOptions,cwl,wdl}.rst
  • [ ] New features without tests.
  • [ ] Comment on the lines of code where problems exist with a review comment. You can shift-click the line numbers in the diff to select multiple lines.
  • [ ] Finish the review with an overall description of your opinion.

Merger Checklist

• [ ] Make sure the PR passes tests.
• [ ] Make sure the PR has been reviewed since its last modification. If not, review it.
• [ ] Merge with the Github "Squash and merge" feature.
  • [ ] If there are multiple authors' commits, add Co-authored-by to give credit to all contributing authors.
• [ ] Copy its recommended changelog entry to the Draft Changelog.
• [ ] Append the issue number in parentheses to the changelog entry.