Description of problem:

When using widgets (ActiveDropdown, ActiveTextInput, ActiveMultiSelect, SchemaUpdater) with fetch:retrigger dependencies, the initial fetch often fails because the dependent fields don't have values yet. This results in HTTP errors (e.g., 404, 400) being displayed to the user on the form, even though this is expected behavior during initial load.

Add a new ui:props option fetch:error:skip that suppresses fetch error display until all fetch:retrigger dependencies have values.