Possible memory leak in Xaml generator

[Youssef1313]

Current behavior

uno/src/SourceGenerators/Uno.UI.SourceGenerators/XamlGenerator/XamlCodeGenerator.cs

Lines 23 to 25 in 772427d

	public partial class XamlCodeGenerator : ISourceGenerator
	{
	private readonly GenerationRunInfoManager _generationRunInfoManager = new GenerationRunInfoManager();

uno/src/SourceGenerators/Uno.UI.SourceGenerators/XamlGenerator/GenerationInfoManager.cs

Lines 21 to 23 in 772427d

	internal class GenerationRunInfoManager
	{
	private List<GenerationRunInfo> _runs = new List<GenerationRunInfo>();

uno/src/SourceGenerators/Uno.UI.SourceGenerators/XamlGenerator/GenerationInfo.cs

Lines 10 to 12 in 772427d

	internal record GenerationRunInfo(GenerationRunInfoManager Manager, int AdditionalFilesHash)
	{
	private ConcurrentDictionary<string, GenerationRunFileInfo> _fileInfo = new();

uno/src/SourceGenerators/Uno.UI.SourceGenerators/XamlGenerator/GenerationRunFileInfo.cs

Lines 9 to 11 in 772427d

	internal record GenerationRunFileInfo(GenerationRunInfo RunInfo, string FileId)
	{
	private Dictionary<INamedTypeSymbol, int> _appliedTypes = new Dictionary<INamedTypeSymbol, int>();

• XamlCodeGenerator holds a reference to GenerationRunInfoManager (this is alone is not good - generators should never have state)
• GenerationRunInfoManager holds a reference to a list of GenerationRunInfo.
• GenerationRunInfo holds a reference to ConcurrentDictionary<string, GenerationRunFileInfo>
• GenerationRunFileInfo has a dictionary that keeps symbols alive, and thus keeps whole compilations alive.

This looks like a memory leak. I don't think we should keep all old compilations alive this way.