feat(ui): add support for disabling join field row types

[akhrarovsaid]

What?

This PR adds a new admin.disableRowTypes config to 'join' fields which hides the "Type" column from the relationship table.

Why?

While the collection type column can be helpful for providing information, it's not always necessary and can sometimes be redundant when the field only has a singular relationTo. Hiding it can be helpful by removing visual noise and providing editors the data directly.

How?

By threading admin.disableRowTypes directly to the getTableState function of the RelationshipTable component.

With row types (via `admin.disableRowTypes: false | undefined OR default for polymorphic):

Without row types (default for monomorphic):

[paulpopus]

My first impression is that we shouldn't introduce an additional config option and instead add something like a _collectionType name to this column so that it can be treated like any other column - controlled via defaultColumns or toggleable by the user via UI

[paulpopus]

@akhrarovsaid Actually, we had a discussion and we landed on having the new admin type to disable it
It should also be disabled by default for non-poly joins

[akhrarovsaid]

Hey @paulpopus

So I've made it disabled by default for non-poly joins. However, a number of tests actually depend on the type column, and instead of rewriting those tests and/or finding every area of the e2e's where the type column is depended on, I've simply added admin.disableRowTypes: false to them so that otherwise they remain unchanged.

I've also added docs & a few tests to show the behavior between monomorphic and polymorphic fields with disableRowTypes.

Let me know your thoughts & thank you!