Move CrankyTokenFilter to the Lucene.Net.Analysis namespace

[NightOwl888]

Is there an existing issue for this?

• I have searched the existing issues

Task description

CrankyTokenFilter was incorrectly placed in the Lucene.Net.TestFramework.Analysis.CrankyTokenFilter namespace. It should be moved to the Lucene.Net.Analysis namespace because it was in the org.apache.lucene.analysis package in Lucene.

[paulirwin]

I was happy to see that this was caught by my in-progress work on the API comparison tool (#1022):

(Namespace/Package mismatches show on either side as a missing type, unless a manual mapping override is added.)

To clarify the original issue, while it needs to be moved to the Lucene.Net.Analysis namespace, it still will be in the TestFramework project, and should not be moved to the Lucene.Net.Analysis.Common project.