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.

Add Entity reference field [#1801304]

Libero Config Get File - Colaboratory

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

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

Custom Action Invalid Argument Error : Entity Reference cannot

No unique index found for the referenced field of the primary

360 Core (Client Center, E-Journal Portal): Release Notes and

Views relationships with multi-valued entity reference fields

Fix the UX of Entity Reference fields [#2116551]

Add Entity reference fields like: User reference, Content

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

Inspect the configured ER component to prevent runtime issues

Add Entity reference field [#1801304]

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

Solved: Business Unit Specific New Contact Form