Reporting Internal View: Review Changes between two arbitrary versions (diff feature)

#### Description:

The BA would need the capacity to review changes made between two versions.
This would be reusing a lot of code from #479

[Context](https://teams.microsoft.com/l/message/19:2f0473607ca24b218de6c500ede9a496@thread.tacv2/1754957025377?tenantId=6fdb5200-3d0d-4a8a-b036-d3685e359adc&groupId=29821293-3244-455d-beae-e01d27762cfe&parentMessageId=1754957025377&teamName=External%3A%20CAS%20-%20Clean%20Growth%20Digital%20Service%20Team&channelName=Metabase&createdTime=1754957025377) in Teams

#### Acceptance Criteria:

Given I am on the [reporting grid ](https://www.figma.com/design/LsDmLDCdnJqI8UahyqvOD8/BCIERS-Designs?node-id=46297-10250&t=kbEv8ScYM11Bcrb1-4)
When I click report history
Then I am taken to the [report history page](https://www.figma.com/design/LsDmLDCdnJqI8UahyqvOD8/BCIERS-Designs?node-id=46264-3264&t=kbEv8ScYM11Bcrb1-4)

Given I am on the report history page
Then I see a dropdown to pick all report version IDs for a report
(for context, business area searches for the report version IDs in Metabase to find reports)

Given I have selected an old report version in the dropdown
When I select an item in the new version dropdown
If the selection is not a newer report,
Then I get the error message: must be a later version

Given I have clicked "Go"
Then I am taken to the review differences page
[Wireframe](https://www.figma.com/design/LsDmLDCdnJqI8UahyqvOD8/BCIERS-Designs?node-id=46245-24150&t=kbEv8ScYM11Bcrb1-4)

I see a "Compare reports" section
With page description "Comparing old report version ID [11] submitted on [July 23, 2025] with [12] submitted on [July 25, 2025]"

#### 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
- [ ] Run `django-silk`
- [ ] 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 existing implementation from issue #479, then inspect the reporting grid, report history and review differences wireframes. Trace how report version IDs are found in Metabase and map the version-selection flow, including rejection of a non-later version. Done means the described navigation, comparison details and acceptance criteria are implemented and tested.

Written by the indexing model from the issue text.