Schema config should prevent creation of circular dependencies

[maxpatiiuk]

1. Create a PickList PrepType
2. Make PickList type be Entire Table and set table to Prep Type
3. Add a default formatter for the Prep Type table that uses the name field.
4. Open Schema Editor for the Prep Type table
5. Assign the PrepType pick list to the name field.

This causes a circular dependency, as formating the name field requires, requires fetching pick list items, which requires formatting the name field and so on.

This caused #2144 and #2145 (comment).

Checking for this case in the Schema Config would be a bit tricky, because when assigning a pick list P for the field F, it needs to check if P has a formatter, and if so if that formatter includes F in it.

[maxpatiiuk]

This could happen not just for pick lists.

Imagine an accession formatter that calls accession agent aggregator that calls accession formatter - not sure how we detect that without limiting useful features and useful workflows (i.e, agent group member displaying group name)

[maxpatiiuk]

With the formatter/aggregator editor being available and so easy to use, and showing a live preview of formatter on any change, this issue is far more likely to happen. And once it does, the front-end will be rapidly sending requests to the back-end.

[maxpatiiuk]

Moved the formatter/aggregator case into a separate issue - #3266