Consider Writing a Suppressor for `CA2000`

[JasonBock]

Describe the solution you'd like

If I have a test like this:

using var context = new RockContext();
var disposable = context.Create<IDisposableCreateExpectations>();
disposable.Methods.Dispose();

iUseDisposable.Use(disposable.Instance());

I get a CA2000 on the Instance() call. Rocks should suppress this because it's expected the developer will use the instance in such a way that the instance will be disposed.

[JasonBock]

May want to also do this for CA2025:

using var response = new HttpResponseMessage
{
  StatusCode = HttpStatusCode.OK,
  Content = new StringContent("5")
};

HttpRequestMessage? requestMessage = null;
object?[]? arguments = null;

using var mockContext = new RockContext();
var messageHandlerExpectations = mockContext.Create<HttpMessageHandlerCreateExpectations>();
messageHandlerExpectations.Setups.SendAsync(
  Arg.Any<HttpRequestMessage>(), Arg.Any<CancellationToken>())
  .Callback((message, token) =>
  {
    requestMessage = message;
#pragma warning disable CA2025 // Do not pass 'IDisposable' instances into unawaited tasks
    return Task.FromResult(response);
#pragma warning restore CA2025 // Do not pass 'IDisposable' instances into unawaited tasks
  });