Problem/Motivation
Currently the Field Type agent splits up the creation or editing fields into for subtasks that are storage setting generation (on creation), field config, form config and display config creation/updating.
The actual prompt that is forwarded for this is for all of them, because most models does not have enough trained knowledge on knowing if the minimum resolution is to be stored in storage settings, field config or form config and gets it wrong sometimes. And we can't feed that on the initial prompt since we don't know the field type then.
The problem with this is that it forwards this request to all of the above and gives back information about if it could do something. And since the form config will not be able to set minimum resolution it will report back this as part of the response to the assistant, which in its turn reports to the end-user.
You end up with a result that it might not have done what your wanted in the form config and that you should change it, even if you actually didn't requiest some changes that effects the forms config.
We can't include storage settings in this, since storage settings might affect the rest, like choosing entity reference type.
This change will make the result come faster and cheaper and be more consistent in not doing warnings about results that are actuall ok.
Steps to reproduce
Proposed resolution
Move those three steps into one step.
Remaining tasks
User interface changes
API changes
Data model changes