This is still needed for running unit tests, but just in one place. We
can remove it everywhere else.

- Reverted FormatCommandHandler.FormatDocument
- Removed option search configuration for code cleanup

We initialize AssemblyName when we create the project with the
project system name (because the workspace requires we have something).
But ocne we get the real path, we need to use the real name.

Our explicit layout was not correct on 64-bit, which we do run these
tests on.

Noticed that we never did this in Roslyn correctly: the fix is simple.

This produces a new free-threaded, well factored API for adding projects
to the VisualStudioWorkspace. The core type is the VisualStudioProject
which is a free-threaded API that you can use to push information over.
CSharpProjectShim, VisualBasicProject and CPSProject each have an
instance of VisualStudioProject that they push things through.

The inheritence model here is now smaller. CSharpProjectShim and
VisualBasicProject inherit from AbstractLegacyProject, but that's it.
CPSProject now inherits nothing, and AbstractProject is here purely
for TypeScript back-compat until they're moved onto the new APIs. The
expectation is F# and TypeScript both move to VisualStudioProject, which
we make public in some form. Then that type will go away.

This ports https://github.com/dotnet/roslyn/pull/28472, that went into the `editorconfig-ide` feature branch, into `dev16.0.x` branch with following additional refactorings/enhancements:

1. Generated .editorconfig file has all localized string as comments.
2. No hardcoding of individual options in the editorconfig file generator. Instead, each `EditorConfigStorageLocation` now requires to provide a delegate to convert a given option value into the .editorconfig string representation (basically complimentary of the parsing delegate that was already required).
3. Introduce concept of `OptionGroup` to enable grouping options in the same feature (such as CodeStyleOptions, CSharpCodeStyleOptions, FormattingOptions, CSharpFormattingOptions, etc.) into sub-features or groups (such as "this. preferences", "expression-level preferences", etc.). This enables the editorconfig generation to group the related options, without explicit knowledge of each option group.
4. Expose `AllOptions` from each option feature (such as CodeStyleOptions, CSharpCodeStyleOptions, FormattingOptions, CSharpFormattingOptions, etc.), so that the corresponding `IOptionProvider` always stays in sync with implemented options.

* Rename target GetBuildVersion to GetVsixVersion

* Targets refactoring to align with Arcade SDK

* Remove unused property

* Use Arcade VSIX build targets

* Upload Willow VSIXes directly from VSSetup directory

* Add setup packages to Roslyn.sln

* Remove swr validation from BuildBoss

* Avoid copying CoreXT packages

* Don't delete DevDivPackages\Roslyn dir

* Upload vsixes even when the build fails

* Clean up VSIX project files

* Install VSIXes in specified order

* Do not set TargetFrameworkVersion.

* Fix parameter

* DevDivInsertion better error message

* Remove 'win' from target string

* Fix dir name

* Install Setup.Dependencies

* Default values for insertion components

* Make BuildBoss happy

* Fix VSIX path

* NGEN binaries that should have been NGEN'd

* RoboCopy returns non-zero exit code on success

* Pass OfficialBuild property to vsmanproj

1. Break the analyzer into two separate diagnostics for flagging unused and unread members. Latter rule has no code fix.
2. Remove all UI option elements for the added diagnostics and turn the rules off by default for now.
3. Bail out for invalid operations and syntax errors.
4. Handle doc comments and nameof - report unread member diagostics instead of unused member diagnostics if referenced in non-read/write context.

* NuGet packaging

* Add missing VS package references

* Fix scripts

* Add comment on Workspace.Desktop references with PrivateAssets

* Fix Microsoft.NETCore.Compilers package

* Fix up references

* Build fixes

* Correct OutputPath for package projects

* Use NuGetRepack to force exact versions in per-build packages

Analyzer flags two cases: members with no read/writes and members with only writes.

1. Members with no read or writes: `Type '{0}' has an unused private member '{1}' which can be removed.`
2. Only writes: `Type '{0}' has a private member '{1}' which can be removed as the value assigned to it is never used.`

Code fix removes the unused member declaration.
Fixes #24225

Open questions:
1. Current analyzer design uses a single code style option for all members and both the above kinds of unused members. We can potentially have multiple options, but this should probably be done based on feedback.
2. Should the analyzer use different diagnostic IDs for the above two kinds of unused members? This will mean that the FixAll experience will need multiple iterations for removing unused members.
3. Should we update the code fix (or have an additional code fix) that also updates the write references for the case (2) above? Or is it better to leave the references to break the code so the user can analyze if the value being assigned can also be removed. The PR current chooses the latter approach as it is more conservative and unlikely to cause silent breaks.

* remove random last token from engine.

* put the support back to what it used to, but in different way.

* PR feedback

* added comments on the typing rule.

* PR feedbacks

* make AbstractObjectBrowserLibraryManager constructor lazier

* PR comments

* readonly and use expression body

Our unofficial packages don't correctly pull in some DesignTime
dependencies (since they always create packages without any
dependencies), but this caused issues once we moved to AsyncPackage
since there's new PIA types being involved. For now, to sort this out
just move back to the official packages which just do the right thing
to start.

As a part of this, I also move us to the official
Microsoft.VisualStudio.SDK.EmbedInteropTypes package; we had our own
clone of the code but it wasn't covering all the assemblies that we
now need to embed as well.