Update project for initial release

[paulirwin]

This PR updates the project in preparation for our initial release under the Apache GitHub organization. It includes:

• Updates NuGet packages and target framework for unit test project
• Adds Sample project to test and debug analyzers
• Adds a launchSettings.json file to allow for debugging the analyzers, and removes VSIX support
• Fixes a failing unit test
• Fixes Roslyn meta-analyzer warnings (as errors)
• Adds GitHub Actions file
• Removes unused CodeFixes project (these will go into the same analyzers project)

[NightOwl888]

Thanks for the PR.

I confirmed I was able to run the tests and hit a breakpoint after the changes.

I noticed that Microsoft uses .ruleset files to group rules together. Since we will have specific rules that will need to be enabled when we upgrade to the next version of Lucene (LuceneDev1000-LuceneDev1004 are all good examples of these) it would be good to be able to group them.

1. Default - for general development
2. Upgrade - only useful when upgrading Lucene
3. Code Search - only useful when searching for complex code patterns that are specific to Lucene's design that are too difficult to do using Find and Replace

I suspect there will be other categories as the project develops.

According to ChatGPT we can use .ruleset files for this purpose: https://chatgpt.com/share/67cfaeeb-72c4-8005-a530-afb1e27cec94

There is also some other stuff to address. Please see the inline comments.

[NightOwl888]

One thing I forgot about in the review was that since this project will be a private dependency of all of the Lucene.Net projects, it should be strong named to avoid the build warning. Ideally, we would use the same SNK from the lucenenet repo, but I see no issue with copying it here, since it is unlikely we will ever change it.

[paulirwin]

@NightOwl888 I split out creating rulesets as apache/lucenenet#1143

Ready for re-review.