modified the after update triggers to link datasets and samples to th…

[DerekFurstPitt]

…eir direct ancestors in a way that no longer recreate the activity and all linkeages. Because the existing implementation involved using query functions that deleted everything, it became necessary to make new query functions to accommodate this change, and now we have a solution that handles each ancestory individual, either deleting or adding.

Also quickly fixed an incorrect log for an unrelated function, that referenced the wrong method. for update_status

[yuanzhou]

@DerekFurstPitt Your implementation looks solid in both logic and coverage. Just two minor points to wrap things up:

• Add INFO log for each case so we know whether new_ancestors or ancestors_to_unlink get handled. Also helpful to add INFO log when no changes to the ancestors detected.
• Remove the comments at

  entity-api/src/schema/provenance_schema.yaml

  Line 465 in 62c41c4

  # Note: link_dataset_to_direct_ancestors() will always delete all the old linkages first

  and

  entity-api/src/schema/provenance_schema.yaml

  Line 1037 in 62c41c4

  # Note: link_sample_to_direct_ancestor() will always delete all the old linkages first

  as they no longer relevant.