Notice of Alteration Filings for BComp

**Story**
As a BComp, I want to file a Notice of Alteration, so that I can maintain the rest of the information about my Benefit Company.

**Background**
When entities incorporate, they need to provide a lot of information upfront about the entity. When they want to change any part of that information, they need to do a maintenance filing.
There are different kinds of maintenance filings - Change of Directors & Change of Address are two separate filings. Notice of Alteration is basically everything else!

**Description**
in a Notice of Alteration filing, the user can change the following pieces of information about the entity:
* Name
* Translation of Name
* Business type
* Share structure
* Add special resolution/court order dates
* Remove pre-existing conditions (if applicable)

**Acceptance Criteria**
See the requirements document here: https://sites.google.com/freshworks.io/bcros/bcomp/notice-of-alteration

Story Level Definition of Ready:

- [ ] Have Stakeholders approved this story?
- [ ] Does User story have full flow of business rules, happy and alternate paths etc. ?
- [ ] Are the dependies known/understood?
- [ ] Dev team accepts user experience artifacts?
- [ ] Are the validation rules defined? (UI, Data, Role-Action)
- [ ] Is a formal UAT required for this user story?
- [ ] Are the acceptance criteria well defined in this ticket (Story level) that QA can confirm or deny ?
- [ ] Does user story need to reference BA checklist? (are functional/Non functional descriptions captured ?)
- [ ] Is the person who accepts this user story as complete identified? (PO)
- [ ] Can this User story be sized by the Dev. team ?
- [ ] Can this User story be demoed to show value?
- [ ] Is this user story small enough to be completed in a sprint?