When an active widget is instantiated, it loads the default data from an endpoint.

So far, when the field contains already a value, such default is ignored in favor of preserving the existing value.

Per customer request, the default will overwrite the field in case when its value has not been provided by the user (means just pre-populated by a former fetch).

This can happen when a SchemaUpdater introduces a field. By a change somewhere, this or another SchemaUpdater replaces the field by another value.

Another use case is when the user enters a value in a field A and the active field B retriggers based on that. The endpoint for the B sends different data. Up to now, the 2nd-round B defaults are not stored to the field B since it already contains something from the previous fetch.

Context: https://github.com/redhat-developer/rhdh-plugins/blob/main/workspaces/orchestrator/docs/orchestratorFormWidgets.md#activetextinput-data-fetching