Expose onIncompatibleSchemaChange properties in materialization workflows

[kiahna-tucker]

Issues

The issues directly below are completely resolved by this PR:
#1375

Changes

1375

The following features are included in this PR:

• Enable the specification-level onIncompatibleSchemaChange property to be configured in materialization workflows. An autocomplete field located in the top-level Backfill section accomplishes this.

• Create a hook which updates the specification-level onIncompatibleSchemaChange property.

• Extend BindingState with an onIncompatibleSchemaChange property that captures the value of the specification-level onIncompatibleSchemaChange property.

• Create a utility function that updates or removes the specification-level onIncompatibleSchemaChange property.

• Enable the binding-level onIncompatibleSchemaChange property to be configured in materialization workflows. An autocomplete field located in the binding-level Backfill section accomplishes this.

• Rename the hook which updates the binding-level onIncompatibleSchemaChange property.

• Extend BindingState with a ResourceConfig['meta']['onIncompatibleSchemaChange'] property that captures the value of the binding-level onIncompatibleSchemaChange property.

Tests

Manually tested

Approaches to testing are as follows:

• Validate that the incompatible schema change section does not appear in capture workflows.

• Validate that the field initialized properly when editing a materialization that has the specification-level, onIncompatibleSchemaChange property set to a supported value.

• Validate that the drafted specification is updated properly when the field is set to a supported value and cleared.

Automated tests

N/A

Playwright tests ran locally

• Admin
• Captures
• Collections
• HomePage
• Login
• Materialization

Screenshots

This field is positioned between the top-level Backfill section and the binding selector.

Spec-level, onIncompatibleSchemaChange field | Empty

Spec-level, onIncompatibleSchemaChange field | Menu options

Spec-level, onIncompatibleSchemaChange field | Option selected

Spec-level, onIncompatibleSchemaChange field | Unsupported value detected | String

Spec-level, onIncompatibleSchemaChange field | Unsupported value detected | Other

[dyaffe]

Thanks, confirming that this looks good to me @kiahna-tucker

[travjenkins]

I struggled with how to name a hook that is for a component... thoughts on keeping the "components are capitalized" rule within the hooks folder?

[kiahna-tucker]

Hmm... I think that works for now. It may be difficult to live with as components are often subject to being relocated and renamed, but we can play it by ear.

[travjenkins]

overall last round of changes to code look good

still gonna try to break it as best I can with testing