Field API: prepare to register 3rd party types

[oandregal]

Part of #73076 and #61084

What

The Field API defines some bundled types. For example, integer, date, etc.

A type is simply a collection of default props: anything a type can do, a field author can. Though, as surfaced in this conversation at #73387 we may still want to allow registering 3rd parties types for convenience.

This issue serves to track work to make that possible.

How

These are things that are not controlled by the field (type) and should:

• Validation. See type checks here. #73642
• DataViews Filter UI. See type checks here. #73922
• Get controls. See type check for type array.
• Filtering in filterSortAndPaginate. This utility contains code for filtering based on different operators. While the code is not type specific, this logic might benefit from being moved to the field (type). #74733

[ntsekouras]

I've started working on the last item of this issue:

Filtering in filterSortAndPaginate. This utility contains code for filtering based on different operators. While the code is not type specific, this logic might benefit from being moved to the field (type).