Allow multiple ways to group fields in UI

Problem/Motivation

Some groupings are not obvious and user may need to go back and forth in the modal to find the correct field.

Users have alternative needs and thought patterns in adding new fields and a single way of grouping fields into field types does not provide good user experience for all user. Several fields have properties that overlap between field type groups and some fields were not clear to group according to the user testing results. Adding contrib module fields will increase the complexity.

With new UI it might be difficult to find Paragraphs (Reference revisions) or maybe Commerce fields (such as "taxnumber") from the mix of fields. A presumably common use case is that a user adds a new module to add a new field type and immediately adds this to be used in a content type.

Proposed resolution

Allow using different points of views to the list of fields.

A simple start would be to allow selecting between current default grouping and by module/package. Otherwise presumed useful groupings would be grouping by 1) common use case (purpose) 2) technical attributes (datatype) 3) module

Remaining tasks

• Add alternate view grouped by module and allow toggling between views
• Get icons from the modules
• Create follow-up issues for alternate grouping views and reviewing current default

User interface changes

Add to field type view in modal tab-like links that allow user to choose from different ways of grouping.
It might not always be pretty, but we could use icons also from the modules themselves as they should be made available to project browser,

API changes

Data model changes

Release notes snippet