Attachments: Catch-all option

#### Description:

Add an "other" attachment type that wouldn't be restricted to only one.
This way reporters can add any kind of additional documentation.

[Wireframe](https://www.figma.com/design/LsDmLDCdnJqI8UahyqvOD8/BCIERS-Designs?node-id=24285-5223&t=Tm9UxVpuejnMzV38-4)

#### Acceptance Criteria:

Given I am an industrial reporter
When I am on the attachment page
And my file doesn't fit any of the categories
Then I have a place to attach it to my report

#### Development Checklist:

- [ ] Checklist item
- [ ] Checklist item
- [ ] Checklist item
- [ ] Meets the DOD

#### Definition of Ready (Note: If any of these points are not applicable, mark N/A)

- [ ] User story is included
- [ ] User role and type are identified
- [ ] Acceptance criteria are included
- [ ] Wireframes are included (if required)
- [ ] Design / Solution is accepted by Product Owner
- [ ] Dependencies are identified (technical, business, regulatory/policy)
- [ ] Story has been estimated (under 13 pts)

#### Definition of Done (Note: If any of these points are not applicable, mark N/A)

- [ ] Acceptance criteria are tested by the CI pipeline
- [ ] UI meets accessibility requirements
- [ ] Configuration changes are documented, documentation and designs are updated
- [ ] Passes code peer-review
- [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
- [ ] Ticket is ready to be merged to main branch
- [ ] Can be demoed in Sprint Review
- [ ] Bugs or future work cards are identified and created
- [ ] Reviewed and approved by Product Owner

#### Blocked By/Blocking

#### Notes:

-

Start by reviewing the attachment page and the linked wireframe to understand the existing attachment categories and the proposed catch-all option. Done means an industrial reporter can attach a file that fits none of the current categories, with the acceptance criteria verified by tests or QA.

Written by the indexing model from the issue text.