Custom Affiliation API name overrides EDA Affiliation API name when Custom API name is an exact match to EDA API name

[jacebryan]

• Feature or bug?
  Feature/Enhancement

• What is the current behavior?
  When a customer has a custom Primary Affiliation API name that matches an EDA custom Primary Affiliation API name (minus the hed namespace) the custom API is reviewed first and the EDA custom API second.

• What is the expected behavior?
  When a customer has a custom Primary Affiliation API name that matches an EDA custom Primary Affiliation API name (minus the hed namespace) the EDA API is reviewed first and the custom API second.

• What is the motivation / use case for changing the behavior?
  Issue was raised in Case# 23540218

Pre-Step:

• Ensure all Primary fields on Contact are exposed

Steps to reproduce:

1. Create a new custom field on Contact called "Primary Organization" (API name = Primary_Organization__c)
2. Expose the new field on the HEDA Contact Page Layout
3. Create a new custom Account Record Type on Account called "Organization Account"
4. Create the Affiliation Mapping:
   Account Record Type = Organization Account
   Contact Primary Affl Field = Primary Organization
5. Create a new Organization Account
6. Create a Contact
7. Create an Affiliation to the Organization Account created in step 5
8. The mapping has been directed to the Primary Business Organization field on Contact rather than the Primary Organization field.

Work Around (using the example above):

1. Edit the API name for Primary Organization and updat it to "Primary_Org__c"
2. Follow steps 6 - 7
3. The mapping has been directed to the Primary Organization field on Contact and NOT the Primary Business Organization field.

[jacebryan]

**lurch: add

[LurchTheButler]

Tracking W-034587