As a user, I can see the AGM Date (or "NO AGM") on the AR in the previous filing history.

**Background**
We have added the ability for co-ops to indicate that they held "no AGM" for a year in an annual report filing. Because of this, it is not instantly clear which annual reports held AGMs and which did not. This might be useful for a user ______.
Because of this, we have decided to add the date that the AGM was held to the Annual Report line item in the previous filing history. If no AGM was held for the year of that Annual Report, and the user indicated that in the filing, once it enters the previous filing history list, the user can see "NO AGM" on the line item. This way, the user does not need to click in to an output to see the date of the AGM, or to see if an AGM was held at all.

**Acceptance Criteria**
* When the user completes an annual report filing, and the filing enters the Previous Filing History list:
* The user can see the date of the AGM, on the AR, from the previous filing history list (if an AGM was held)
* The user can see "NO AGM", on the AR, from the previous filing history list (if an AGM was NOT held)

See the following section of the google site for detailed requirements:
[Co-ops](https://sites.google.com/freshworks.io/bcros/co-op/annual-report): Section 1. ANNUAL REPORT FILING **>** Section 2. Business Requirements **>** Line 3 "Ledger"
and
Section 4. NO AGM (Without Extension) **>** Section 3. Business Requirements **>** Line 4 "Ledger"

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?