Scan for middleName vs middleInitial across all entities work

I found that Edit UI uses "middleName" for various persons (NR applicant/directors/completing party/proprietor, etc), but the Legal API `parties` endpoint returns "middleInitial" instead. This may impact corrections, alterations and changes.

Symptoms include:
- a person's middle name/initial is not displayed in the person's table
- a person's existing middle name/initial is not displayed when changing/editing that person
- schema error on filing if middleInitial isn't present
- others, unknown atm

This needs to be looked into and resolved somehow...
- what are we going to call this field?
- does a schema need to change?
- does Legal API endpoint need to change?
- do UIs need to change?
- do existing filings (in Dev/Test/Prod) need to be data-corrected?

Feedback from business:
- We need to be consistent on how we treat these fields for other entities too, across the board.
- Middle Initial and Middle Name are optional fields
- Align with regulatory and policy requirements - if any in place.

**To Do List:**

- [ ] Scan all the UI's and API's to identify where individual names are and what they use - first, middle, last, middle initial
- [ ] Create a spreadsheet of all the different places and open a new ticket to address next steps