Firm Registration - First Name too long breaks Completing Party Validation

- Keyclock is our access system.
- Keyclock does not have a middle name field.
- Every time an end-user logs in using either BC Services Card or BCeID, and if at the source there is a middle name, Keyclock will concatenate the incoming first and middle name values into the first name.
Example:
BC Services Card
Last Name: Dinu
Middle Name: Vasile
First Name: Mihai
Keyclok
Last Name: Dinu
First Name: Mihai Vasile
**Impact on BC Registries filings**
- The login name values automatically become the name elements of the Completing Party.
- For Firms Registrations, the Completing Party is a pre-populated, non-editable component.
- A recent RAID ticket also concluded that even Staff cannot edit a Completing Party section for firms
- When first name and middle name combined, have more than 30 characters, they will break the Firm Registration Completing Party validation.
- Also, some users refused our system behaviour of listing their middle name value as first name

WHAT TO DO:
Phase 1
- Right now Completing Party is used for all corporation types, and because of the COLIN synch, there is a 30 chars limit on all CP name fields.
- Create a new Completing Party component, just for firms.
- Because firms are not synched back to COLIN, update the length of the First Name field to 50 chars (for example)
- This still does fix the issue of the first name and middle name values being in one field, but if client does not complain, this is a win.

Phase 2
- Interventions to be done, outside of the Entities Team, at the Keyclock and Auth Web levels, to present the Entities logged in user with last, first, and middle names