Show legacy record data in A&R front end

## Description

Based on [BRS-816: Migrate historical data into A&R system](https://bcparksdigital.atlassian.net/browse/BRS-816)
, all legacy parks/subareas and most records should already be visible in the system. This change is to ensure that the new `Legacy Data` activity and any other historical activities are visible to the FE.

As a user, I want to be able to see legacy records for all subareas activities, even if that subarea doesn’t have that activity in its current config (ie - subarea used to have `Day Use`, but then `Day Use` was removed from the subarea, despite there still being `Day Use` records in the system). The current system only fetches activity records if the subarea is currently configured to have that activity.

In some cases with historical data, and particularly with the Legacy Data activity, the current system will not fetch these records.

## Acceptance Criteria:

`Legacy Data` and other legacy activity records are surfaced when that particular date/park/subarea combination is queried.

## Notes

## Linked issues
blocks

- [ ] https://github.com/bcgov/bcparks-ar-admin/issues/270

created by

- [x] [BRS-680](https://bcparksdigital.atlassian.net/browse/BRS-680)

is blocked by

- [x] https://github.com/bcgov/bcparks-ar-api/issues/237
- [x] [BRS-971](https://bcparksdigital.atlassian.net/browse/BRS-971)

is cloned by

- [x] [BRS-972](https://bcparksdigital.atlassian.net/browse/BRS-972)

Start by tracing the current front-end query for records by date, park, subarea, and activity, then review the dependency on bcparks-ar-api issue 237. Done means Legacy Data and other historical activity records appear for the requested date/park/subarea even when the activity is no longer in the current configuration.

Written by the indexing model from the issue text.