Fix(Migration): fix skip orphaned relation items copy #21555
                
     Closed
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Checklist before requesting a review
Please delete options that are not relevant.
Description
Fix : !39723
Currently debugging the handling of orphan links in ImpactRelation.
I noticed that the check to determine whether the source or destination exists (and skip if not) relies on the following function:
By default, it loads an empty object if the item is not found in the database, and therefore does not return
falsewhen missing.This seems to cause the skip logic for this relation to behave incorrectly.
Submitting the PR as-is to observe the behavior in the unit tests.
Screenshots (if appropriate):