Change ingestion input to JSON lines format

[ohltyler]

Description

This PR updates the ingestion input format to JSON lines format: https://jsonlines.org/. This is a more standard data file format for persisting JSON data, and makes it easier for importing.

More details:

• adds new JsonLinesField component, which is similar to JsonField but has specific logic around error handling and formatting to be specific to JSON lines.
• changes file upload type extension to be *.jsonl instead of JSON inputs
• adds new JSON lines config field type and corresponding schema/value presets
• updates all instances of the ingest docs parsing to handle a JSON lines string instead of a JSON array string
• bug fix: missing parameters on processorConfigsToTemplateProcessors. Externally, this has no impact.

Demo video, showing the new input type, validation, error handling, and successful ingestion:

screen-capture.26.webm

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[ohltyler]

IT fixed by opensearch-project/opensearch-dashboards-functional-test#1732

[kamingleung]

@ohltyler Can we add a learn more external link in the helper text? Users who are not familiar with JSON lines can learn more about it.
Something like:
Documents must be in JSON lines form. Learn more[icon]
Goes to https://jsonlines.org/

[ohltyler]

@ohltyler Can we add a learn more external link in the helper text? Users who are not familiar with JSON lines can learn more about it. Something like: Documents must be in JSON lines form. Learn more[icon] Goes to https://jsonlines.org/

Yes, good idea :)

[ohltyler]

Dynamically display multiple error messages if found (currently defaulting to 3):

[kamingleung]

Dynamically display multiple error messages if found (currently defaulting to 3):

@ohltyler Nice, does the list update dynamically if users fixes an error or a new error came up?

[ohltyler]

Dynamically display multiple error messages if found (currently defaulting to 3):

@ohltyler Nice, does the list update dynamically if users fixes an error or a new error came up?

The list is cleared until users click out of focus again - this keeps any performance or lag issues from occurring, in addition to low-level details like line numbers becoming stale as users make changes.

[kamingleung]

@ohltyler Do you have a quick demo video on multiple error messages?

Inline validations feels much more clear and intuitive to me. Although this coder editor doesn't support inline validation, we should invest into an editor that support modern code editing patterns.

However, this shouldn't be a blocker to JSON lines.

[ohltyler]

@ohltyler Do you have a quick demo video on multiple error messages?

Inline validations feels much more clear and intuitive to me. Although this coder editor doesn't support inline validation, we should invest into an editor that support modern code editing patterns.

However, this shouldn't be a blocker to JSON lines.

screen-capture.27.webm

Sure. And strongly agree, which is why I've brought this up again in opensearch-project/OpenSearch-Dashboards#2875