LCFS - Transfer is categorized upon director recording

Description: The system categorizes the transfer upon director recording (i.e., approval).

From the date on which the written agreement to transfer credits was reached between the two organizations (a user input) and the date the director records the transfer, the transfer will fall under one of 3 categories:

Category A: The agreement to transfer was reached within the last 6 months.
Category B: The agreement to transfer was reached between 6 months to 1 year ago.
Category C: The agreement to transfer was reached more than 1 year ago.

Category D: There is also a Category D checkbox override. This is based on the analyst or director selecting a checkbox which will override the Category A-C date calculation. This functionality is handled in another card: https://app.zenhub.com/workspaces/low-carbon-fuel-standard-644c2db3be098a001977ad0b/issues/gh/bcgov/lcfs/257

Upon director recording a transfer, the predictive language for the categorization in the transaction history section should be replaced with the final category. The predictive language is developed in a different card (#258). See wireframe for mockup of final category.

Wireframe: https://preview.uxpin.com/59145260c7d8cc48969ac79401cc03d84843c3d9#/pages/165112777/simulate/no-panels

Purpose and benefit to user: Categorizing transfers is used to provide more accurate market pricing information to stakeholders. As transfer agreements can be negotiated at different times (recently vs. months ago vs. years ago), the reported price may not reflect current market prices. Transfers that are negotiated months or years ago are separated out from more recent transfers to better represent market prices over time. Market data is posted in a spreadsheet at the bottom of our Credit Market page: https://www2.gov.bc.ca/gov/content/industry/electricity-alternative-energy/transportation-energies/renewable-low-carbon-fuels/credits-market

Acceptance Criteria:

Given I am a director or analyst, When I record a transfer, Then the transfer should be automatically categorized into Category A, B, or C based on the date the agreement was reached, or Category D if the override checkbox is selected.
Given I am a user viewing the transaction history, When a transfer has been recorded by the director, Then the predictive language indicating the expected category should be replaced with the final category (A, B, C, or D).
Given I am a user accessing the Credit Market page, When I view the market data spreadsheet, Then I should see the transfers categorized appropriately, reflecting accurate market pricing information over time.

Development Checklist:

[ ] Implement logic to categorize transfers into Categories A, B, or C based on the date difference between the current date and the date the transfer agreement was reached.
[ ] Review the TFRS codebase related to this categorization. The logic will be pretty much a copy over.
[ ] Add functionality for a Category D override, which can be selected by an analyst or director, bypassing the date-based categorization.
[ ] Ensure that once a transfer is recorded, the predictive language in the transaction history is updated to show the final category (A, B, C, or D).
[ ] Update the page's spreadsheet to display transfers with their respective categories, ensuring accurate representation of market data over time.
[ ] Conduct thorough testing to ensure that the categorization works correctly in all scenarios, including edge cases.
[ ] Implement necessary UI updates as per the wireframe to reflect these changes in categorization and display.
[ ] Ensure proper documentation and comments are added to the code for future maintainability.

Notes:

The override functionality (Category D) should be clearly documented and restricted to authorized personnel only to prevent misuse.

bcgov / lcfs