Allow users to set the split policy of related records to 'duplicate related objects' when the relationship is based on GUID to GUID fields.
Currently ArcPro only allows the split policy to be set to 'duplicate related objects' if the relationship is based on a GlobalID parent key field and a GUID foreign key field. However Esri Sweet and other non-Esri database systems require a GUID parent key field and a GUID foreign key field to work, so the duplicate split policy can't be set for these relationships.
Not being able to set the split policy to 'duplicate related objects' leads to loss of related records from all but the largest feature when it is split.
