Rename long tables to fit in DuckDB

[jdangerx]

Overview

Duckdb table names have a character limit of 63. We have four tables that exceed 63 characters:

core_eiaaeo__yearly_projected_fuel_cost_in_electric_sector_by_type: 66
core_eiaaeo__yearly_projected_generation_in_electric_sector_by_technology: 73
core_eiaaeo__yearly_projected_generation_in_end_use_sectors_by_fuel_type: 72
out_eia923__yearly_generation_fuel_by_generator_energy_source_owner: 67

We should rename these resources, enforce the resource name length constraint earlier in the code and update our documentation.

Success criteria

• These four tables make it into DuckDB
• The names are updated in our documentation - which means also running a patch release so that the default stable docs show the new names

Next steps

Preview Give feedback

1. come up with shorter names