Support different input transform types

[ohltyler]

Description

Continuation of #493. Opening to a feature branch so main stays stable. This PR breaks the advanced transform modals entirely.

This PR completes the new UX flows for configuring input transforms. At a high level, this adds support for:

• toggling between different transform types (static value vs. field vs. JSONPath transform vs. template)
• configuring JSONPath expressions / transforms via new modal
• configuring templates (and any sub-transform mappings) via new modal

Implementation details:

• updates the schema for the input map - this means changes in the UI config, Formik form, and yup schema to be compatible. Basically, we introduce a new field for each input map entry, called transformType, which allows dynamic rendering of different form components based on the type selected. For example, selecting 'Field' will offer a dropdown of the available document or query fields. Selecting 'String' will show a freeform textbox.
• refactoring and re-creating a lot of the existing MapField component logic inside of the newly-refactored ModelInputs component, but entirely customized for the input map, since it requires too much custom logic to remain a generic component, and was getting overloaded with props anyways. Note: later on, we will likely clean up all of these props, as the generic form is still used for other processors, such as the text chunking processor's field_map field. Also, copies over some of the logic from MapArrayField to dynamically render a 'Configure' button if the map is empty.
• adds new ConfigureExpressionModal to configure the JSONPath expression in a dedicated modal. Copies over some of the data fetching & transform logic from the existing InputTransformModal, but now it is just at a per-field level.
• adds new ConfigureTemplateModal to configure a template, as well as any sub-transform variables that can be injected in the template. Copies over some of the data fetching and transform logic from the InputTransformModal, and ConfigurePromptModal.
• updates the QuickConfigureModal to support the new config such that quick-configure values are populated in the input map appropriately
• changes in the conversion util fns (config -> form, config -> schema, etc.) to account for the schema changes. Adds logic to parse out some of the values and bucket them into model_config fields (if static), or input_map values (if dynamic). Takes any transforms defined under templates and adds them to the underlying input_map.
• additions to constants and interfaces to account for the schema changes

Testing

• confirmed underlying ML processor configs handle all new transform types successfully
• confirmed configs can build and produce working ingest / search pipelines

Demo video:

screen-capture.7.webm

screen-capture.7.webm

Issues Resolved

Makes progress on #491

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]

Tests will be updated later; this is all just going to a feature branch for faster iteration.

[saimedhi]

@ohltyler, I am not able to play the Demo video. Could you add it again please?

[ohltyler]

@ohltyler, I am not able to play the Demo video. Could you add it again please?

Sure, added again. Working fine from chrome for me.