Increase info/debug logging in Storage SDK

[rickle-msft]

Logging is limited to a very narrow set of operations right now--mostly to exceptions thrown with a bit more information in the retry policy about interactions on the network. It will help improve debugging if we make more liberal use of info and debug log levels to capture discrete steps in parallelized operations, etc.

Also of note, we should log the string to sign used in generating a sas. Customers frequently get 403s when using a sas, and it can be difficult to guide them getting the string to sign used by the sdk. Logging this would make troubleshooting these bugs much easier. The string to sign used for sas shouldn't contain any sensitive information, either.

[github-actions]

Hi @rickle-msft, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.