[FEATURE] Provide way of defining configuration for the pipeline

[martin-gaievski]

Is your feature request related to a problem?

As part of adding explainability for hybrid query (#658) we going to add a new response processor for handling explanations from the normalization processor. Additional steps in configuring that processor are required from the user. This isn't an error prone approach.

What solution would you like?

Template of the default pipeline configuration that is created by the system itself and is based on information provided by developer/engineer together with the code of new feature.

What alternatives have you considered?

Simplified version of the solution may be: a dependency between processors. If one processor depends on another processor, then that foundational/child processor is added to the pipeline configuration (or just executed) by the system. Such "depends on" relation can be part of the processor registration.

Example:
Can be extension for Factory class

it already accepts the map of processor factories final Map<String, Processor.Factory> processorFactories, but it can only return one instance of the Processor class. Factory can return collection of the processors depending on what it needs.

Do you have any additional context?

Logged similar issue for core opensearch-project/OpenSearch#15921