Port existing ETL logic to Dagster

[jdangerx]

Scope

• adding dagster/dagit itself
• adding SQLite, FERC-specific SQLite, and Parquet IO managers
• moving EIA, FERC, EPA-CEMS ETL processes over to dagster

# Punchlist for merging into dev
* [ ] #2303 
* [ ] #1874 
* [ ] #2223 
* [ ] #2309 
* [ ] #2272 
* [ ] #2301 
* [ ] #1873 
* [ ] #2296 
* [ ] #2286 
* [ ] #2292
* [ ] #2300 
* [ ] #2322 
* [ ] #2318 
* [ ] #2352 
* [ ] #2368 
* [ ] #2294 
* [ ] #2295 
* [ ] #2306
* [ ] #2396 
* [ ] #1872 
* [ ] #2356 
* [ ] #2419 
* [x] Merge pre-Dagster dev into main
* [x] Tag a final pre-Dagster commit/release
* [x] Notify key outside contributors
* [x] Merge #2104 into `dev`
* [x] Do a demo / walkthrough internally
* [x] Merge `dev` into existing working branches
* [x] Publicize the change and hold office hours

[bendnorman]

I think this is the remaining work to get dagster-asset-etl merged into dev:

• [ ] #2296. This will allow us to produce the ETL outputs on dev and dagster-asset-etl in the same environment so we can diff the data. #2294 Seems like @jdangerx is on this.
• [ ] #2301 @zschira we could work on this together.
• [ ] I am working on #1872
• [ ] I need to create an issue for comparing sqlalchemy schemas so people don't get unexplained database errors when the metadata changes.
• [ ] #2295

[zaneselvans]

I think this is basically done and could be closed. Maybe we should post an announcement in GitHub Discussions and do some Tweetes.