Schema: amalgamation application (3 sub-types)

[severinbeauvais]

We should be able to do this while other work is ongoing, ie, it should only block the submission of the filing (not creating or saving draft).

• add name enum value = amalgamationApplication to filing schema already exists
• add amalgamationApplication schema
• add enum type for 3 variations (see restoration for example):
  • "regular"
  • "vertical"
  • "horizontal"
  • (data is the same for all 3 variations but we need to know what type this amalgamation is... possibly for UI, outputs, etc)
• add amalgamatingBusinesses object/array; needs to contain:
  • amalgamating companies (that are in Lear)
    • business ID
    • role -- whether it's the holding company
  • foreign amalgamating business (jurisdiction, name, corp num)
• add business name/type object - can this reuse existing nameRequest object? YES
• add addresses object (same as IA)
• add contact information object (same as IA)
• add directors object (same as IA)
• add share classes object (same as IA)
• add court order object (same as IA)
  • optional
  • does not contain file number
  • does contain effectOfOrder which is either "" or "planOfArrangement"

This is what's been implemented so far in Create UI. There may some missing data still but it's a good start.
https://github.com/bcgov/business-create-ui/blob/1ec5d9a485cc3afbdf13577391f71eec4c3718c8/src/interfaces/filing-interfaces/filing-interfaces.ts#L22

[jdyck-fw]

Figure out the extra details with support from Argus and Mihai.

[jdyck-fw]

Consider breaking this up as we learn more about the schema needs.

[severinbeauvais]

Yes to current courtOrder object.

Also there's a new property for courtApproval (null or True or False).