Add test to ensure user provided source/target fields take precedence
also consider that you mentioned that this behavior would change for multiple mutations. is this a breaking change related to this issue? https://github.com/Azure/data-api-builder/pull/2051#discussion_r1512176170
please also fill out the details of the issue.
also does this issue address the concern of https://github.com/Azure/data-api-builder/pull/2051#discussion_r1514436388
The check for count of referencing/referenced columns being 0 is removed before adding ReferencingColumn/ReferencedColumn information. Adding details about why it is okay to remove this check will be helpful in the future if we were to look at this logic in the future.
This needs more details added before implementation