As a Co-op, I want to be able to file more than 1 Annual Report per year

### As a Co-op, I can file more than 1 AR per year
## Description:
Coops are allowed to file more than 1 AR per year at a later date.

**Dependencies**

**Acceptance Criteria**

**Validation Rules**

Ready to Build (DoR):
- [ ] Stakeholders have approved
- [ ] User story completed
- [ ] What are the dependencies
- [ ] Validation rules defined (UI, Data, Role-Action)
- [ ] Is a formal UAT required

Acceptance / DoD:
- [ ] Design / Solution accepted by Product Owner
- [ ] Acceptance criteria has been defined (happy path, known sad paths)
- [ ] Test coverage acceptable
- [ ] Peer Reviewed
- [ ] Accessibility reviewed and acceptable [checklist](https://github.com/bcgov/entity/docs/coding-standards/accessibility.md)
- [ ] UX Approved
- [ ] PR Accepted
- [ ] Production burn in completed

The issue names no files, tests, entry points, dependencies, or validation rules. Start by clarifying the annual-report business rules and reviewing the repository's JavaScript, Python, and PostgreSQL flows for filing annual reports. Done should include agreed happy and sad paths, UI, data, and role-action validation, plus acceptable test coverage.

Written by the indexing model from the issue text.