Change log level of hash message

[plannigan]

Minor change. It seemed odd that this was the only log message in the entire code bash using log() directly. As a result, it was not effected by the verbosity level.

I'm open to using a different log level. I went with info() as it would not change the currently default behavior.

Changelog-friendly one-liner: Adjust log level for PyPI hash message.

Contributor checklist

• Provided the tests for the changes.
• Assure PR title is short, clear, and good to be included in the user-oriented changelog
• Assure one of these labels is present: backwards incompatible, feature, enhancement, deprecation, bug, dependency, docs or skip-changelog as they determine changelog listing.
• Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

[atugushev]

Nice catch! I'd prefer debug though:

[atugushev]

LGTM 👍

[plannigan]

There were a few test cases that explicitly checked for the log message. With the move to debug, they were failing because it was no longer being written. I updated the test cases to check for no message being written as it is the smallest change. A different option would to to remove the output check, as I don't think explicitly checking for log messages provide much value.