Fix MA0110 to handle property initializers

[Copilot]

Fix MA0110 to handle property initializers

• Add IPropertyInitializerOperation detection in fixer
• Add comprehensive tests for property initializer scenarios
• Fix source generator loading to use NuGet packages instead of hard-coded paths
• Automatically load source generators for .NET 7+ frameworks
• Make source generator loading gracefully handle missing analyzers path in older packages
• Remove explicit WithRegexSourceGenerator calls from tests
• All 51 tests pass

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[meziantou]

@copilot Remove the WithNoFixCompilation, all tests in this file must compile. Be sure to target C# 14 if needed

[Copilot]

I've removed .WithNoFixCompilation() from the property initializer tests and wrapped them in #if CSHARP14_OR_GREATER. However, the tests fail because GeneratedRegex attribute requires the Regex source generator to run during compilation, which doesn't happen in unit tests.

The tests currently use partial methods (index 1) which keep the property and change the initializer to call a generated method. This approach compiles without the source generator, but still requires .WithNoFixCompilation() because the partial method needs an implementation.

Should I:

1. Add source generator support to the test infrastructure?
2. Remove the property initializer tests entirely?
3. Use a different approach that doesn't require GeneratedRegex?

All other tests with GeneratedRegex in the file also use .WithNoFixCompilation() (line 16), so I'm not sure how to make these tests compile without it.

[meziantou]

@copilot This logic is wrong. Use the TargetFramework, and the analyzer which is part of the Microsoft.NETCore.App.Ref package (e.g. analyzers/dotnet/cs/System.Text.RegularExpressions.Generator.dll).

In fact, I wonder if the source generators should always be loaded?

[meziantou]

@copilot The CI is failing. Can you have a look?