Fixes #3572 and some others: Remove analyzers from solution

[dodexahedron]

This PR removes the enum source generator projects, code, pwsh module, and CI build item from v2.

The generated code from the v2 code at the base of this branch was copied into normal source files so that existing uses can be preserved.

Note that, if you change one of those enums, you need to add an entry to the FastIsDefined method's switch expression for that enum's extension class. Enum changes are considered breaking changes in the .net world, anyway, however.

Those files will get deleted at whatever point in the future I come back to the generators. Probably during beta.

Fixes

• Fixes Some more prep for revamped sourcegens and CI #3572
• Fixes Simplify workflow surrounding roslyn projects #3494
• Fixed v2 crashes on run with missing dependency JetBrains.Annotations #3544 in my environment, but not an explicit goal of this PR
• Fixes Analyzers -> Restarting VS when simply changing branches is not acceptable. #3477
• Fixes Analyzers project builds with warnings #3466
• Fixes Can't build the current v2_develop branch 37f59d2 #3450
• Postpones Create source generator to pimp our enums #3443

Proposed Changes/Todos

• Remove analyzer projects
• Remove analyzers from CI build
• Remove Terminal.Gui.PowerShell.Analyzers PowerShell module
• Preserve currently used generated code
• Other miscellaneous cleanup mandated by the above

Pull Request checklist:

• I've named my PR in the form of "Fixes #issue. Terse description."
• My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
• My code follows the Terminal.Gui library design guidelines
• I ran dotnet test before commit
• I have made corresponding changes to the API documentation (using /// style comments)
  - Not relevant
• My changes generate no new warnings
• I have checked my code and corrected any poor grammar or misspellings
• I conducted basic QA to assure all features are working

Ready to go

[BDisp]

LGTM. I switch from develop and this PR branches and rebuild on both and it is working as expected without needing to run any scripts. Thanks.

[dodexahedron]

Good to hear.

I had tried in a couple of environments as well, but still wanted to be extra-sure I wasn't just getting lucky. 😅

I was originally splitting them off into a local nuget package but decided it wasn't worth wasting the effort on that since I'm already going to be doing something similar but not identical when I get back to it in the formal public nuget package I'll be putting out eventually.

Just wanted to work on other more important stuff for now and make your workflows easier in as simple a way as possible. There are other ways to alter your workflow that would have avoided the pain you guys were feeling, but it didn't feel worth altering those habits for something temporary.

[tig]

LGTM!

Thank you. Thank you. Thank you.

[BDisp]

@dodexahedron It looks like you removed the unit tests. It would be beneficial to create them in the UnitTests project, but using TestHelpers to normalize the newlines regardless of whether the WSL tests are using the Windows 11 file system or not.

[BDisp]

You removed it here in #3600 but it's again on the v2_develop.

Terminal.Gui/Terminal.Gui/Terminal.Gui.csproj

Lines 62 to 66 in 7dc12a4

	<ProjectReference Include="..\Analyzers\Terminal.Gui.Analyzers.Internal\Terminal.Gui.Analyzers.Internal.csproj">
	<PrivateAssets>all</PrivateAssets>
	<OutputItemType>Analyzer</OutputItemType>
	<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
	</ProjectReference>

[dodexahedron]

I removed the analyzer project and its tests, yes.

Didn't remove the actual TG UnitTests project.

But good thought on reformatting and whatnot. I'll add what's necessary to make ReSharper ignore those files as part of #3558 too, so it doesn't change things.