Dispose of streams that are created to wrap BinaryData

[MatthewSteeples]

Certain overloads for blob storage create streams to wrap the bytes that are sent in. These Streams are not disposed which means (unless I've misunderstood something) they'll hang around for longer than required and cause additional pressure for GC.

There are no breaking changes, and no changes to any API surfaces (internal or external).

EDIT: Just realised I was getting IDisposable and Finalizers confused, so my comment above about extra GC pressure is incorrect. It's not necessary for these Streams to be disposed of (as MemoryStream doesn't deal with any unmanaged resources) so it's just down to whether it's considered good practice I believe.

[github-actions]

Thank you for your contribution @MatthewSteeples! We will review the pull request and get back to you soon.

[amnguye]

/azp run net - storage - ci

[azure-pipelines]

No pipelines are associated with this pull request.

[github-actions]

Hi @MatthewSteeples. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[github-actions]

Hi @MatthewSteeples. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing /reopen if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the no-recent-activity label; otherwise, this is likely to be closed again with the next cleanup pass.

[azure-sdk]

API change check

API changes are not detected in this pull request.