Add hollow types for deprecated UI controls

[SimonZhao888]

Fixes #3783

API review

notes - #3783 (comment) and in the video

Proposed changes

Add controls removed in NET3.1 Back to .NET10 for binary compatibility.

• None of the re-added types can be constructed, all constructors throw new PlatformNotSupportedException(), default constructors are suppressed by introducing throwing public constructors if needed.
• All attributes that have been present on the .NET Framework types, are preserved, as they are accessible by reflection.
• All re-introduced types are decorated with [EditorBrowsable(EditorBrowsableState.Never)] attribute that hides them from the intellisense. Type names can be typed in by the developer manually and intellisense would show the same members as it did for .NET Framework projects.
• All re-introduced types are decorated with the ObsoleteAttribute that results in a compile time warning. All types share a single deprecation warning Id, to simplify suppression, but have different explanation messages.
• All re-introduced types are decorated with [Browsable(false)] attribute to not show custom control properties of these types in the property browser.
• All public members are re-introduced with their metadata, except for the private attributes.
• Members inherited from the base classes (Control, for example) are not re-introduced even if they had been overridden in the past because they are not required for binary compatibility, unless they are decorated with different attributes.
• Members that are re-added to the existing types (Form and Control) are returning defaults or doing nothing.
• Non-void public or protected instance members on the restored types throw null, not the PlatformNotSupportedException to save space.
• Void public or protected instance members do nothing.
• Public or protected fields return default values.
• Nullability is disabled for all re-added classes, structs and delegates for compatibility with the .NET Framework.

Test methodology

• manually
• added a new project that targets .NET Framework UnsupportedTypes that instantiate all re-added types. This project is referenced from the unit test assembly. Unit tests verify that methods from NETFX assembly can be resolved, and types are type-forwarded to the hollow implementation in NET10 instead of throwing the missing member exception.
• compared NETFX public surface generated by Microsoft.DotNet.GenAPI.Tool SDK tool against NET10 public surface generated by the same tool

Microsoft Reviewers: Open in CodeFlow

[codecov]

Codecov Report

Attention: Patch coverage is 24.62094% with 1044 lines in your changes missing coverage. Please review.

Project coverage is 76.09947%. Comparing base (2b2ce68) to head (355118f).
Report is 14 commits behind head on main.

Additional details and impacted files

@@                 Coverage Diff                 @@
##                main      #10913         +/-   ##
===================================================
- Coverage   76.21334%   76.09947%   -0.11388%     
===================================================
  Files           3197        3227         +30     
  Lines         640464      641831       +1367     
  Branches       47220       47252         +32     
===================================================
+ Hits          488119      488430        +311     
- Misses        148825      149852       +1027     
- Partials        3520        3549         +29     

Flag	Coverage Δ
Debug	76.09947% <24.62094%> (-0.11388%)	⬇️
integration	18.10449% <0.32086%> (-0.07023%)	⬇️
production	50.02050% <11.33690%> (-0.13523%)	⬇️
test	96.98515% <52.22222%> (-0.05365%)	⬇️
unit	47.45664% <11.33690%> (-0.09235%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

[ricardobossan]

LGTM

Copilot reviewed 52 out of 67 changed files in this pull request and generated no comments.

Files not reviewed (15)

• Winforms.sln: Language not supported
• src/System.Windows.Forms/src/System/Windows/Forms/Controls/Unsupported/DataGrid/DataGridColumnStyle.cs: Evaluated as low risk
• src/System.Windows.Forms.Design/src/System/ComponentModel/Design/Serialization/CodeDomComponentSerializationService.CodeDomSerializationStore.cs: Evaluated as low risk
• src/System.Windows.Forms/src/System/Windows/Forms/Controls/Unsupported/ContextMenu/ContextMenu.cs: Evaluated as low risk
• src/System.Windows.Forms/src/System/Windows/Forms/Controls/Unsupported/DataGrid/DataGridLineStyle.cs: Evaluated as low risk
• src/System.Windows.Forms.Design/src/System/Resources/Tools/StronglyTypedResourceBuilder.cs: Evaluated as low risk
• src/System.Windows.Forms/src/GlobalSuppressions.cs: Evaluated as low risk
• docs/list-of-diagnostics.md: Evaluated as low risk
• src/Common/src/Obsoletions.cs: Evaluated as low risk
• src/System.Windows.Forms/src/System/Windows/Forms/Control.cs: Evaluated as low risk
• src/System.Windows.Forms/src/System/Windows/Forms/Controls/Unsupported/ContextMenu/MenuItem.cs: Evaluated as low risk
• src/System.Windows.Forms/src/System/Windows/Forms/Controls/Unsupported/ContextMenu/Menu.cs: Evaluated as low risk
• src/System.Windows.Forms/src/System/Windows/Forms/Controls/Unsupported/DataGrid/DataGridBoolColumn.cs: Evaluated as low risk
• src/System.Windows.Forms/src/System/Windows/Forms/Controls/Unsupported/DataGrid/DataGridColumnStyle.CompModSwitches.cs: Evaluated as low risk
• src/System.Windows.Forms/src/System/Windows/Forms/Controls/Unsupported/ContextMenu/MenuMerge.cs: Evaluated as low risk

Comments suppressed due to low confidence (1)

src/System.Windows.Forms/src/System/Windows/Forms/Controls/Unsupported/ContextMenu/Menu.MenuItemCollection.cs:58

• [nitpick] Add a comment for the AddRange method to maintain consistency with the rest of the code.

public virtual void AddRange(MenuItem[] items) { }

[Tanya-Solyanik]

To the copilot comment -

Add a comment for the AddRange method to maintain consistency with the rest of the code.

I'm not adding comments to re-added methods inside the re-added types.

[JeremyKuhne]

Looks good!