Improve ingest node usability

[martijnvg]

There are number of improvements and bug fixes that improve the usability of ingest node. This meta issue includes a number of those fixes that should be done in the short to medium term.

• Make name setting template-able in pipeline processor. See FR: Add interpolation to pipeline processors in the Elasticsearch ingest node #39955
• Add origin pipeline name to on_failure processor metadata. See Add origin pipeline name to on_failure processor metadata #44920
• Add pipeline name to ingest metadata. See Add pipeline name to ingest metadata #42106
• Bulk script upsert are executed after pipeline execution. See ingest: bulk scripted_upsert runs the script after the pipeline  #36745
• Fail when accessing _id in pipeline when id is auto generated. See Ingest processor cannot access _id on autogenerated id #41163
• Fail fast when specifying two processor type inside a single processor object element. See ingest: processors configuration can too easily be misconfigured resulting in non-deterministic processor execution order #36134
• Support pipeline processor in simulate api without requiring to create the pipeline it refers to. See ingest: Support multiple pipelines from _simulate without creating actual pipelines #35495
• Allow Tika parsers to be configured from attachment processor. See ingest-attachment PDF-processing should be configureable #36890
• Make the output date format of the date processor configurable. See Add option to output nanoseconds in date ingest processor #42523
• Support RFC7231 UserAgent scheme in User Agent processor. See Support RFC7231 UserAgent scheme in User Agent processor. #41001
• The put pipeline api should be able to create multiple pipelines in single API call. Bulk create multiple ingest pipelines #35889
• Add support for if_seq_no and if_primary_term to ingest. See Add support for if_seq_no and if_primary_term to ingest #41255

[elasticmachine]

Pinging @elastic/es-core-features (:Core/Features/Ingest)

[dakrone]

This has been open for quite a while, and we haven't made much progress on this due to focus in other areas. For now I'm going to close this as something we aren't planning on implementing. We can re-open it later if needed.