LCFS - Relabel and Correct Dates for Legacy Transactions (Aggregator Issuance)

**Describe the task**
Identify all transfers currently labelled as "legacy transactions" that were created to support aggregator-related historical data entry for the 2022 and 2023 compliance periods. **Excel sheet highlighted with these is in the Teams Card Attachment folder.**

Update these records to reflect a more accurate label (e.g., “Aggregator Issuance”) and correct associated metadata, including agreement date, recorded date (if required), and compliance period year.

**Purpose**
- These transactions are currently mislabelled, which creates confusion for analysts and reduces clarity for compliance review and audit.
- Relabelling and correcting dates ensures alignment with the original intent of the transactions, improves transparency, and supports audit defensibility.

**Acceptance Criteria**
- [ ] All identified “legacy transactions” related to aggregator historical work are relabelled to a clear and consistent name (e.g., “Aggregator Issuance”)
- [ ] Agreement date, recorded date (if applicable), and compliance period year are corrected and validated (2022 or 2023 as appropriate)
- [ ] Changes do not impact credit balances or transaction integrity
- [ ] Updated transactions are reflected consistently across relevant tables, views, and reporting outputs

**Additional context**
- These transactions were created as part of historical data entry approaches used to accommodate aggregators prior to full system functionality
- Consider whether a formal transaction type or controlled label should be introduced to distinguish these from other legacy or migrated records