Override Stream ReadAsync/WriteAsync Analyzer

[NewellClark]

This fixes issue #33789.

I ran the analyzer against dotnet/runtime and found several violations:

• DeflateStream, ChunkedMemoryStream, RequestStream, and NetworkStreamWrapper were all trivial, and have been dealt with in this PR.
• CryptoStream was non-trivial, and is being worked on in this PR.
• DeflateManagedStream is internal, and calls into the IFileFormatReader interface, which is also internal. I was unable to find any classes that actually implement this interface throughout dotnet/runtime.
  We could do what we're doing for CryptoStream and check if the Memory<byte> is actually an array, and if not simply do the copy, but since this interface is internal, I figured we might be able to explore other options.
• WebSocketHttpListenerDuplexStream is also internal, and from what I could find, ReadAsync/WriteAsync are only ever called from WebSocketBase, which only calls the array-based override. Unfortunately, WebSocketHttpListenerDuplexStream also calls back into WebSocket, and it passes the array it was given into multiple different methods on WebSocket, and some methods on WebSocketBuffer. Providing memory-based overrides would require almost a complete rewrite of WebSocketBuffer as well as changes to code that consumes it. Since nothing currently calls the memory-based overrides on WebSocketHttpListenerDuplexStream, I think we should strongly consider suppressing the warning.

[mavasani]

@NewellClark Seems like your PR has many more changes then intended.

[mavasani]

The target branch seems to be incorrect dotnet:merges/master-to-release/6.0.1xx-preview1. Did you intend to target master or release/6.0.1xx-preview1?

[NewellClark]

Did you intend to target master or release/6.0.1xx-preview1?

Oops, so I did. I will fix it.