Custom analysis can't have same names as built-in

[mayya-sharipova]

Do not allow custom analysis components to have the same names as
built-in components

Closes #22263

[elasticmachine]

Pinging @elastic/es-search

[jpountz]

I think we should still allow overriding the default, default_search and default_search_quoted analyzers, since this is the way that we document that default analyzers can be set at the index level? https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis.html

[mayya-sharipova]

@jpountz Thanks for the feedback, Adrien. This has been addressed in the 2n commit.

[markharwood]

@mayya-sharipova - a heads-up. I'm about to introduce the first out-of-the-box normalizer ("lowercase") in #53882

Like pre-built analyzers, pre-built normalizers should be something we want to avoid name-clashing with user-defined configurations in index settings.

[mayya-sharipova]

@markharwood Thank you for the heads-up. I will adjust this PR accordingly

[mayya-sharipova]

@markharwood I have decided that is better to tackle name clashing for normalizers in a separate PR, and normalizers are absent in PrebuiltAnalysis against which we checking name clashing. To put normalizers into PrebuiltAnalysis, we may need to introduce PreConfiguredNormalizer class and do some additional work.

[mayya-sharipova]

@jpountz Can you please continue the review when you have time.

[elasticsearchmachine]

Hi @mayya-sharipova, I've created a changelog YAML for you. Note that since this PR is labelled >breaking, you need to update the changelog YAML to fill out the extended information sections.

[javanna]

the changelog creation triggered notifcations on some of these old PRs, maybe it's a chance to close them though? :)

[elasticsearchmachine]

Pinging @elastic/es-search-relevance (Team:Search Relevance)