Use a child of FieldConfigEditForm when adding a new field

For now, the child class does not override anything in the parent. As long as we work with the child class, we should not break anything having to do with editing existing fields.

Closes #3386762

added 2 commits

• 6a42db63 - Use a child of FieldConfigEditForm when adding a new field
• 401db8dd - Override getFormId()

Compare with previous version

added 1 commit

• 3e3f861f - Move some code to the new child class

Compare with previous version

added 1 commit

• bd535235 - Move some code to the new child class

Compare with previous version

added 1 commit

• d66a6754 - Move some code to the new child class

Compare with previous version

added 1 commit

• 7159bc15 - Remove unused property $entityDisplayRepository

Compare with previous version

added 1 commit

• 441b08d1 - Remove unused property $entityDisplayRepository

Compare with previous version

added 4 commits

• a2d1ee10 - Move deletion of temp store to the child class
• 8af85b0e - Move the $tempStore property to the child class
• 3434f4e3 - Move FieldStorageCreationTrait to the child class
• 41d09015 - Remove $entityDisplayRepository property from the parent class

Compare with previous version

added 1 commit

• 67d99ce8 - Update FieldConfigEditForm instantiationnin the unit test

Compare with previous version

added 1 commit

• de26ca7f - Move the $tempStore property to the child class

Compare with previous version

closed

mentioned in merge request !10062 (closed)