Prevent potential loss of associated contribution data when a Pledges, Memberships, or Participant Registrations are merged

Currently if a user merges a dupe contact which has "paid" membership or event registration transactions or pledges with completed pledge payments - the associated contribution records may be lost if the user doesn't ALSO select Contributions to be merged.

The merge code should automatically carry over to the primary contact record any contributions that are joined to those transactions if Contributions are not selected for merging. Check / merge the following join tables and referenced contribution records:

• membership_payment
• pledge_payment
• participant_payment