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.

Deleting References

How to Enforce Selection of Published Contents in Entity Reference

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

Custom Action Invalid Argument Error : Entity Reference cannot

Add Entity reference field [#1801304]

No search fields to select when creating an entity reference view

Custom Action Invalid Argument Error : Entity Reference cannot

Error in Action for missing values

How to Enforce Selection of Published Contents in Entity Reference

Entity Reference Ajax Formatter

Add Entity reference field [#1801304]

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

Solved: Resource at '/sites.html/content' not found: No re

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