NoConstructorArgumentsForInterfaceMockAnalyzerTests has a doppleganger test to ensure that it doesn't flag a user's class that happens to also be named Mock<T>. We should:
- Expand this scenario to cover all analyzers (probably with extended TestData?)
- Ensure we cover all the entrypoints to Moq
NoConstructorArgumentsForInterfaceMockAnalyzerTestshas a doppleganger test to ensure that it doesn't flag a user's class that happens to also be namedMock<T>. We should: