Move TestApiConsistency rules into Dev Analyzers

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Task description

We should move the TestApiConsistency rules from being unit tests into being Dev Analyzers instead (in the https://github.com/apache/lucenenet-codeanalysis-dev repo). This will allow contributors to catch those issues earlier, as they're typing code in the IDE or at least building, instead of later at unit test runtime. It will also allow us to suppress the findings if there are justifiable exceptions more easily.

We should create one rule per rule enforced by the tests, unless there's a good reason to combine them or split them further.