MHR| Submitting Party in Transfers

### Problem Statement
The submitting party is captured late in the transfer workflow, after owners are added or removed. This differs from other transactions. When an owner is removed during a transfer, that owner can no longer be selected as the submitting party. Users must manually re enter details since historical owners are not available as selectable options.

### Current State
In transfer workflows, owners are added and/or removed before submitting party details are captured.

Submitting party selection occurs late in the workflow (at the review and confirm step), after ownership changes are confirmed.

When an owner is removed during the transfer, that owner is no longer available for selection as the submitting party.

As a result, staff are required to manually re enter submitting party details.
This differs from other transaction types, where submitting party information is captured earlier and remains selectable.

### Potential Risks

- Submitting party details are entered incorrectly due to manual re entry.
- Staff effort and transaction completion time increase.
- Inconsistent behavior across transaction types creates confusion.
- Data quality risks arise when submitting party information does not align with actual transaction context.

### Desired Outcomes

- Submitting party information is selectable at an appropriate point in the workflow (preferably before the ownership information is edited).
- Submitting party logic supports transfer scenarios where owners are added or removed.
- Transfer workflows align with submitting party behavior used in other transactions.
- Historical or removed owners remain available for selection where relevant.
- Submitting party details are captured consistently and accurately without need for manual re entry.