LCFS - Aggregator Issuance Transactions Not Displayed Correctly in UI or Excel Export

*Describe the Bug**
When filtering the Transactions table by the transaction type "Aggregator Issuance", no transactions are displayed in the portal UI. Additionally, transactions that appear to be aggregator issuance transactions are still labelled as "Standalone" transactions in the Excel export. The transaction export now also appears to return significantly fewer records than expected.

**Expected Behaviour**
When "Aggregator Issuance" is selected in the transaction type filter:
- Matching aggregator issuance transactions should be displayed in the Transactions table.
- Aggregator issuance transactions should be correctly labelled in the UI and Excel export.
- The transaction export should include all relevant transactions available to the user.

**Actual Behaviour**
- Selecting "Aggregator Issuance" in the transaction type filter returns no visible results in the Transactions table.
- Transactions continue to be labelled as "Standalone" in the Excel download.
- Downloading legacy transactions from the portal returns approximately 381 transactions, whereas previously more than 1,000 transactions were available.

**Implications**
- Users cannot validate or review aggregator issuance transactions through the portal UI.
- Transaction data may appear inaccurate or incomplete in exports.
- Reporting and reconciliation activities may be impacted if transaction types are incorrectly labelled or filtered.
- Users may incorrectly assume aggregator issuance transactions are missing when they may only be hidden or misclassified.

**Steps To Reproduce**
Steps to reproduce the behaviour:
User/Role: Compliance Unit / Transaction User

1. Go to the Transactions page.
2. Open the transaction type filter.
3. Select "Aggregator Issuance".
4. Observe that no transactions are displayed in the UI.
5. Download the transaction Excel export.
6. Review exported transaction types.
7. Observe that transactions are labelled as "Standalone" rather than "Aggregator Issuance".
8. Download legacy transactions from the portal.
9. Compare the number of returned transactions to previous exports and observe the reduced transaction count.

Notes: is there more work that needs to be done by an analyst to find the correct effective dates for these legacy/standalone transactions? If the 381 left are still requiring dates, I can do this. Just need to know if the original card and highlighted attachment date changes were made. Thanks!

Start by reproducing the issue on the Transactions page with the "Aggregator Issuance" filter, then compare the UI results with the Excel and legacy transaction exports. Trace where transaction types are mapped and where export records are limited or filtered. Done means matching transactions appear in the UI, are labelled "Aggregator Issuance" in exports, and the legacy export includes all relevant records.

Written by the indexing model from the issue text.