Add extra data columns to HIFLD grid CSVs beyond those required by PowerSimData

[danielolsen]

🚀

• Is your feature request essential for your project?

Describe the workflow you want to enable

Add extra data columns to HIFLD grid CSVs beyond those required by PowerSimData.

Describe your proposed implementation

The change can be as simple as expanding the list of columns that are written via the top-level orchestration function, or not filtering the columns at all.

Additional context

The corresponding PowerSimData issue to be able to properly interpret CSVs with extra columns is Breakthrough-Energy/PowerSimData#567.

[danielolsen]

Adding extra data columns also helps with issues like #227, since:

1. We can generate better solar and wind profiles if we can associate our plant table entries with the richer EIA unit information that's available for solar and wind plants within Form 860. Table 3.1 is generator data for all generators, Table 3.2 is additional wind-specific data, and Table 3.3 is additional solar-specific data.
2. Without adding extra columns, the only way (?) to be able to look up the corresponding entries after the grid is made is to encode both the Plant Code (int) and the Generator ID (str) as the plant table index, but
3. PowerSimData expects that the plant table index is integers, to be able to create new indices when adding generators, storage units, etc.

EDIT: now that I think about this a bit more, I think we can get the best of both worlds if we use the full data tables created during Grid CSV creation as inputs to the profile creation, before we filter out all non-PowerSimData columns.

[danielolsen]

I think this is effectively achieved via #256, since the create_grid function now returns tables with all columns, and optionally writes just the ones required for PowerSimData, so I think we can close this.