Fix the UX of Entity Reference fields [#2116551]

Problem/Motivation [#1757452] added config entities back into the selection here, after this was deliberately taken out in [#1801304] taken out of the UI since the initial ER pach didn't support config entities. This leads to completely silly lists of possible things to reference like this: Here you have your "90% case" stuff (Content, Users, Files, etc.) buried hopelessly in amongst a bunch of "1% or less case" stuff like "Editor" and "Text format" and "Breakpoint group." This needs to be fixed, because it makes what's already a challenging field to use about 600x more difficult.

How to Enforce Selection of Published Contents in Entity Reference

8 - How to display entity label using entity reference field

no unique index found for the referenced field of a primary table

Source: For Each Message: Object reference not set to an instance

Solved: VISA: (Hex 0xBFFF0011) Insufficient location information

8 - Entity Reference: Filter by an entity reference view not

Step by step guide, Entity Reference Views Select

Prioritize 'add existing' in nested entity creation UX to prevent

Fix the UX of Entity Reference fields [#2116551]

Keyword-based faceted search interface for knowledge graph

BMC Helix Remedyforce: “ENTITY_IS_LOCKED, This record is locked

drupal - How can I limit an entity reference selection to a

UD Field Assistance - Post E9->E10 Migration - ERP 10 - Epicor

8 - View for Entity Reference reverse, backwards forwards - Drupal

Solved: Business Unit Specific New Contact Form