CA2022 Special-case MemoryStream and UnmanagedMemoryStream and don't issue diagnostic

[buyaa-n]

Special-case MemoryStream and UnmanagedMemoryStream where if we can prove the target Stream is one of those we don't issue diagnostic. Those, in particular the former, are commonly used and we know they are actually safe for this usage; I'd like to avoid causing a lot of noise around them. While we don't necessarily document it's safe, we also don't need to cause folks to do a lot of work in response.

          Can we special-case MemoryStream and UnmanagedMemoryStream where if we can prove the target Stream is one of those we don't issue diagnostics?  Those, in particular the former, are commonly used and we know they are actually safe for this usage; I'd like to avoid causing a lot of noise around them. While we don't necessarily document it's safe, we also don't need to cause folks to do a lot of work in response.

Originally posted by @stephentoub in #7208 (comment)

[paulomorgado]

Make sure Microsoft.IO.RecyclableMemoryStream is not excluded.

/cc @benmwatson