Remove isPrimary from uniq field for carry & clone config

[CarolineDenis]

Fixes #6229

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone

Testing instructions

• Open Collecting Event data entry form
• Add required field
• Add a collector
• Set its isPrimary field to true
• Save
• Open the carry forward config dialog
• Open the carry forward config dialog for the relationship Collector
• Verify you can check and uncheck isPrimary field
• Keep is primary checked
• Carry forward the record
• Verify the isPrimary as been carried over for the collector

Notes:
Since isPrimary field has an override attribute hidden=true in our code even if you uncheck is hidden in the schema config (which will affect other places) it will still stays a hidden field in this context

[emenslin]

• Verify you can check and uncheck isPrimary field
• Verify the isPrimary as been carried over for the collector

isPrimary is hidden in the carry forward config even though it is unhidden in the schema config

03-18_11.28.mp4

[CarolineDenis]

@emenslin, it's because isPrimary has the property override { visibility: 'hidden' } in the code
So even if you change it in the schema config (which will affect other places) it will not change the hidden property in this config dialog.

[emenslin]

@CarolineDenis, changing it would be great! I think since we are adding the ability to check and uncheck it that it should not be hidden so users can see the change

[emenslin]

• Verify you can check and uncheck isPrimary field
• Verify the isPrimary as been carried over for the collector

After discusssing how unhiding isPrimary would break other things it looks good

[combs-a]

• Verify you can check and uncheck isPrimary field
• Verify the isPrimary as been carried over for the collector

---

Everything worked fine on my end. 👍