Stop assigning isPrimary at form layer

Stop assigning isPrimary at form layer

Despite the comments we are actually leaning into isPrimary in the templates.

However, the assigning of it is handlied in the Event_WorkflowMessage_ParticipantTrait
- which looks up the value from the record.

Note that there is some test cover of emails for mulitple participants