DataForm: centralize edit logic in field type definitions

[oandregal]

Part of #59745
Follow-up to #64164 and #64168

What?

Centralizes the edit logic for fields into the field type definitions.

Why?

Follows suit what we did for validation and sorting.

How?

Moves the DataForm controls to the corresponding field type definition.

Testing Instructions

• With the "quick edit" experiment enabled, visit the Pages page.
• Switch to the table view, select a row (multi-selection also works), and open the quick edit action.
• Modify the values and verify that it works as expected.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: oandregal <[email protected]>
Co-authored-by: youknowriad <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[youknowriad]

Putting this one here, means we should also put the DataViewsProps here rather than collocating by the file. So far for this kind of components we kept the types collocated though.

[oandregal]

In 40043fc I collocated DataFormProps back into the component.

DataFormControlProps still lives in the types file: it's required there and there are multiple places where it's used (every type definition). Is there a better place for this one?