Allow user to change contact type of existing contact

[exalate-issue-sync]

Business Reason

Acceptance Criteria

BA notes:

1. if contact type changes, does transaction history change (especially for amendments)?
2. If history remains the same, with contact on the transactions being the type they were when the transaction was created (or amended), then contact type change MIGHT be just (system) adding a new contact with the new type (but how would that affect Updates and build system in preparation for Sprint 0 #4 below?)
3. If history does change, then we have to look at every transaction with that contact
   1. If the transaction supports that contact type, then change the type of the transaction and add/remove the data elements accordingly
   2. If the transaction does not support that contact type….then????
4. After contact type changes, if you look up the contact in your contact list and want to see all transactions, do you expect to see ALL transactions for that contact, both before the change and also after the change?

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1872

[exalate-issue-sync]

gregg.moreland commented: [~accountid:61b0b42cd5986c006a9e1c94] I have put a lot of my thoughts in the ‘BA notes’. My ‘guess’ is that we wouldn’t change any history, but make sure if we have an amendment, we know what to do. Also, no matter what we do, we probably would need to let the user see ALL transactions for that contact regardless of contact type (I can see most common would be an Individual changing to a Candidate, or remotely an org changing to committee).