Add Nested DesignerHost Logic to DemoConsole for Handling Control Names

[ricardobossan]

.NET version

.NET 9.0.100-preview.5.24307.3

Did it work in .NET Framework?

Yes

Did it work in any of the earlier releases of .NET Core or .NET 5+?

No response

Issue description

The current implementation of DemoConsole is missing the nested DesignerHost logic responsible for generating unique control names. This logic is present in the InProc designer but absent in DemoConsole, which causes issues such as duplicate component names when working with controls like BindingNavigator. Specifically, the error arises when attempting to add multiple ToolStripSeparator items, which results in exception due to duplicate component names. This issue does not occur in runtime applications, including those targeting .NET Framework and .NET 9.0.

The absence of this logic in DemoConsole leads to a runtime bug that needs to be addressed.

Steps to reproduce

1. Run the DemoConsole app.
2. Attempt to add multiple ToolStripSeparator items to the BindingNavigator control.
3. Observe that the app throws a System.InvalidOperationException due to duplicate component names.

[ricardobossan]

Status update: #12005 (comment)

[Zheng-Li01]

The issue also can reproduce for MenuStrip/ToolStrip controls in the DemoConsole application.