Create rulesets for dev analyzers

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Task description

Context: https://github.com/apache/lucenenet-codeanalysis-dev/pull/1#pullrequestreview-2671980160

From @NightOwl888:

> 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

Start with the linked pull-request review and inspect how the repository currently configures its development analyzers. Define .ruleset files for Default, Upgrade, and Code Search, then verify that LuceneDev1000-LuceneDev1004 are grouped appropriately.

Written by the indexing model from the issue text.