Add the table list component to the relationship field

[ToneseekerMusical]

Having the option to display documents in a relationship field in the table list component would be incredibly useful for fields with a large number of relationships, allowing for easy viewing and management (when bulk operations are added) of the contained information.

Now, relationship fields that contain relationships from multiple collections that have different datasets could get messy, so it should be only allowed to be used on relationship fields that pull from one collection, or where the collections share an arbitrary minimum number of fields other than _id. Some relationship fields this could be used on would be wholesale and retail orders, user role based profiles, and products in different categories that share a common parent category.

    {
      name: 'relationshipField',
      type: 'relationship',
      relationTo: 'collectionSlug',
      required: true,
      hasMany: true,
      admin:{
        **display:'table/relationship',**
    },

The default values of the admin:display option would dynamically change based on the hasMany flag and the type value of the relationTo field. If hasMany is set to true, and relationTo is a string then it should default to the table list, all others should default to the current relationship field. If hasMany is set to true but relationTo is an array, having display set to table should throw an error if the data structure of the collections doesn't match at least X fields other than _id.

If hasMany is set to true and relationTo is an array, the columns that can be shown in the table should be limited to only the fields the two collections have in common.