Add an ability to choose what type members use within constructor generation

[EmilyGraceSeville7cf]

Environment data

dotnet --info output:

.NET Core SDK (reflecting any global.json):
 Version:   3.1.302     
 Commit:    41faccf259  

Runtime Environment:    
 OS Name:     Windows   
 OS Version:  10.0.18362
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.1.302\

Host (useful for support):
  Version: 3.1.6
  Commit:  3acd9b0cd1

.NET Core SDKs installed:
  3.1.302 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

VS Code version: 1.47.2 (user setup) C# Extension version: v1.22.1

OmniSharp log

Steps to reproduce

• Click type name
• Generate constructor...

Expected behavior

Expected behavior is smth like in Visual Studio:

Actual behavior

There is no any ability to choose what type members use within constructor generation. It is not convenient for big types.

[jmarolf]

Today we just "select all" for the members and not show the UI when we detect we are running in VS Code. Long term we will want to implement our own VS Code based presentation of this dialog. @ryzngard who has been thinking about this area.

[EmilyGraceSeville7cf]

Are there any updates to this issue? 🌝