Upgrade Data Fetcher configuration with dynamic validated pickers

[RebbePod]

Summary

• embed the Flow Config Editor Kit inside the Data Fetcher package
• migrate text and numeric configuration inputs to reusable literal-or-Flow-resource pickers
• replace both object selectors with metadata-driven object pickers that default to user-facing objects, optionally show all accessible objects, and load additional results while scrolling
• make Sort By Field depend on the selected primary object, with an optional custom literal or Flow resource
• make Additional Fields a non-sortable multi-select while preserving removal and selected-field visibility, with an optional custom comma-separated field list
• validate pasted and restored Flow resources against required types and scalar/collection shape
• validate saved field selections after metadata resolves and reject incomplete or nonnumeric Number literals
• show contextual errors naming the selected value, actual type/cardinality, required input shape, and corrective action
• preserve existing Flow property names, metadata types, saved values, references, and generic mappings
• retain legacy internal bundles for package-upgrade safety
• include Apache-2.0 provenance for the embedded framework and synchronize Salesforce metadata on API 67.0

Upgrade compatibility

This is an in-place custom property editor migration. The runtime Data Fetcher component and its public Flow properties remain unchanged. Existing literals, references, object API names, field names, comma-separated field lists, and T/S generic mappings continue to rehydrate through the editor. Existing mappings take priority; missing mappings receive the established fallback so older and newly added components remain activatable.

Known incompatible saved values now receive actionable validation. References and field paths whose metadata is not yet available remain accepted until Flow Builder can resolve their type, avoiding speculative rejection of legacy configuration.

The legacy internal combobox and object-picker bundles remain packaged for upgrade compatibility even though the new editor no longer renders them.

Validation

• npm run test:unit
• 18 test suites passed
• 168 tests passed
• targeted ESLint passed for the migrated editor and embedded framework
• framework npm run verify passed with 176 tests
• Credential Scanning Analysis passed
• SAST passed

[salesforce-cla]

Thanks for the contribution! Before we can merge this, we need @RebbePod to sign the Salesforce Inc. Contributor License Agreement.

[jdayment]

@RebbePod I just pushed an update to /dataFetcherObjectPicker to handle null labels I don't think this will impact your functionality but can you validate the change and I can merge your updates. Also will need to you to sign the contributor license agreement linked above before I can merge.

[RebbePod]

Ok👍

I just made a bunch of minor improvements. It's tricky updating everything in two places.

We should also do in depth testing, both from a fresh install and from previous versions to make sure it upgrades cleanly.

[RebbePod]

@jdayment ready to push and test the changes