Move more token filters to analysis-common module

[martijnvg]

The following token filters were moved: delimited_payload_filter, keep, keep_types, classic, apostrophe, decimal_digit, fingerprint, min_hash and scandinavian_folding.

Relates to #23658

[jpountz]

I left a commet about how to handle GetTermVectorsIT, otherwise it looks good. Maybe @nik9000 has an idea how to handle such tests?

[jpountz]

how hard would it be to keep this test in core by plugging in a mochk payload filter?

[nik9000]

It all depends on if you are testing the term vectors API (stay in core with a mock) or if you are testing something super specific to this token filter. If it is specific, then I'd move it over.

[nik9000]

We ESIntegTestCase subclasses to end in either Tests or IT when they are outside of core but since they don't need the Elasticsearch I like to name them like Tests instead of IT.

[martijnvg]

I'll try move this test back to core and use a mock payload filter.

[martijnvg]

@jpountz @nik9000 I moved the test to core and added a mock payload tokenizer.
I was unable to use Lucene's MockPayloadAnalyzer because the test relies on specifics of DelimitedPayloadTokenFilter, so I end up coping it here. I think this is ok, since it is a small and not too complex token filter

[nik9000]

I think I was trying to keep them in alphabetical order.... No big deal.

[martijnvg]

I re-arranged the lines in alphabetical order.

[nik9000]

It all depends on if you are testing the term vectors API (stay in core with a mock) or if you are testing something super specific to this token filter. If it is specific, then I'd move it over.

[nik9000]

We ESIntegTestCase subclasses to end in either Tests or IT when they are outside of core but since they don't need the Elasticsearch I like to name them like Tests instead of IT.

[nik9000]

I'd prefer

else {
    return false;
}

Just a bit more balanced looking. No big deal either way I guess.