Batch Edit: Add support for editing to-one dependent relations

[sharadsw]

Component of #4929, after #5413

• Allow batch editing to-one dependent fields
• Include support for nested to-one (dependent) fields
• Enable rollback for to-one dependent fields

Additional context from #4929

These relationships get directly updated, and are not matched. If the to-one is not in the db, it'll create one.
This also includes collectingevent when embedded.

Test cases to consider:

• When mapped, the record is directly updated.
• When mapped, if the record is not present, it'll be created, if not null values are present.
• If the record previously had values, and the values are removed (making the cells completely empty), the to-one dependent record will be deleted. Since it is possible that there may be other fields in the database (but not in the query), we may accidentally delete the record. Example: user selected collectionobject -> collectionObjectAttribute -> remarks. And say they set remarks to empty in the spreadsheet, it is is possible that integer1 field in collectionObjectAttribute may have some value. To prevent accidental deletion, by default, we look at all the fields in the database for that record (other than system fields), to determine whether we can delete the record or not. This behaviour is controlled by a remote preference.