LCFS - Create backend 'Compliance Reporting' calculation tables

**Dependencies:**

- The compliance reporting data model and API endpoints will be handled first and in different cards (confirm with Justin)
- Create backend tables for all the components that go in to compliance reporting calculations for the 2024 reporting period.

**Description:**
Develop new compliance reporting calculation backend tables populated with information needed for compliance unit calculations performed in organization's annual (and quarterly) compliance reports for the 2024 reporting period.

In the following order, include the following tables:
- Carbon Intensity Limits #529
- Energy Effectiveness Ratio #530
- Default and Prescribed Carbon Intensities #531 (check if Justin wants these separate like in TFRS)
- Energy Densities #532
- Fuel Types #533
- Fuel Categories #534
- End use #535 (Check with Justin if this End use table is needed for any reason)

**Purpose and benefit to user:**
To create a backend specific feature for all the components needed for calculating compliance units in organization's compliance reports. The information projected in these tables is managed by devs only.

Note: This is setting up for a future feature that will allow IDIR access to an editing function similar to the fuel code feature using AG Grid tables.

**Acceptance Criteria:**

- [ ] Given I am a , When I am , then
- [ ] Given I am a , When I am , then

**Development Checklist:**
- [ ] A
- [ ] B
- [ ] C

**Notes:**

Start by confirming the dependency order and open questions with Justin, then review cards #529-#535 for the requested calculation tables. Done means defining the 2024 backend tables for the listed compliance-reporting components, but the acceptance criteria and development checklist are still placeholders; no files or tests are named.

Written by the indexing model from the issue text.