Add iso code columns to the GHG Emissions module's data downloads

[SARodrigues]

This PR is the frontend counterpart to adding an ISO code column to data downloads.

While the Data Explorer's CSV downloads come from our API (with the exception of Pathways, which is downloaded from a third party API), the GHG Emissions CSV is generated by the frontend, based on the data passed onto the table.

Implementation choices

Because the data displayed and the data downloaded won't necessarily be the same anymore, I see two options:

1. Add a getDownloadData selector
   • the existing getTableData could make use of it and simply remove the iso in order to parse the data for the table
     I feel this would be confusing for future development as it would deviate from the implementation in other modules
2. Add the iso to the existing getTableData selector
   • and add a mechanism/prop in the general table component to allow us to hide the new column

In this PR I opted for the second option because:

• it requires the least amount of code changes; less probability of introducing bugs
• it keeps the selectors' implementation consistent with other modules
  getData returns chart data, getTableData returns table data, CSV downloads are still based on the latter
• we get a new reusable mechanism to use in other modules in which the tabular data displayed may not be consistent with the downloadable data (and the latter is generated in the frontend)

Caveats

I'm not exactly the biggest fan of conditionally adding the iso to the data based on the model in this way (done because we'll only need the iso when the user has chosen to show the data by either countries or regions, but not sectors or gas) nor specifying the columns in this way .

I've pondered a similar implementation to the one in the data explorer, but it feels like it would be bug prone due to the usage of GHG_TABLE_HEADER in places such as here. Worth considering in the future, but perhaps not now due to limitations.

How to test

• Visit: http://localhost:3000/ghg-emissions
• Ensure that, when the user clicks the "Download current data button":
  • When the user has selected to show data by "Countries" or "Regions"
    • The resulting CSV includes the ISO code
  • When the user has selected to show data by "Sectors" or "Gases"
    • The resulting CSV does not include the ISO code
  • The table itself (columns in particular) remain unchanged

[what-the-diff]

PR Summary

• Introduction of Hidden Columns Configuration in Emissions Component
  Our team modified the Greenhouse Gas (GHG) Emissions Component, specifically allowing certain columns to be hidden depending on the requirements. This ensures that only relevant data is displayed, leading to quicker and more efficient analysis.

• Model-Specific Data Handling in Emissions Selector Table Data
  There's an update in the Emissions Selector Table Data, adding a condition that checks if the model in use is 'regions'. This makes data loading dynamic, showing different sets of data based on the model selected, providing a more customized and user-specific experience.

• Modification of Default Column Order in GHG Emissions
  A revision has been made to the original column ordering in the GHG Emissions by including 'iso'. This adjustment has reconsidered 'iso' as a valuable contributor to the dataset representation.

• Hidden Columns Configuration and Filtration in Table Component
  The team has added a feature in the Table Component where hidden columns can be predefined and effectively filtered out. So, columns that are deemed as less necessary can be hidden right away, making data representation cleaner and less cluttered.

[SARodrigues]

Note: the model is also regions when the user selects to show data by Countries

[SARodrigues]

I'm not 100% sure about this.

I mostly wanted to avoid the activeColumns implementation altogether to prevent bugs, as it seems to rely on the column labels to end with the NotShow string. Because it affects other modules and due to time constraints I worked around this, though I believe it'd be ideal to refactor it in the future.

[Bluesmile82]

Yes, maybe we can filter that column before it arrives to the table-component in the future

[SARodrigues]

No actual changes here, automated VSCode changes due to ESlint config.

[Bluesmile82]

Thanks! Not sure if the hiddenColumns is the clearest option for the developers to understand this columns go only to the download, but as you say maybe this is the option with the less changes so probably the best for this case