Use ETS heat pump COP from GMT sys-params

[vtnate]

Any background context you want to provide?

We were unintentionally not allowing users to change ETS heat-pump COP values. That is now available

What does this PR accomplish?

• Read cop_c and cop_h values from a sys-param file
  • Enabled possibility of reading any ETS data from sys-param file in the future
• Change 2 buildings' ETS COP values in the 13-building upstream sys-param file for demonstration/validation purposes
• Fix a few typos
• Update all sys-param files to have fifth-gen ETSs attached to the buildings. This was a copy/paste mistake originally

How should this be manually tested?

• Run the 13-building upstream demo file using the CLI on the command line
• Review the terminal output of final ets_data: for cop_c and cop_h.
  • While most will be 3.5 & 2.5 respectively, there should also be a 3.4 & 2.6, as well as a 3.0 & 3.0, demonstrating that TN is reading from the sys-param file and applying the values to the ETS object correctly.

What are the relevant tickets?

Screenshots (if appropriate)

[mitchute]

Looks good, but it would be good to add a test here. I merged in multi-ghe locally and ran tests, and they all passed. I think once we have a test for the changes in this branch, I'm good.

[vtnate]

Looks good, but it would be good to add a test here. I merged in multi-ghe locally and ran tests, and they all passed. I think once we have a test for the changes in this branch, I'm good.

Ahh, right. I have the json file to show the changes, but I never actually made an assertion for it. I'll make that happen. Thanks Matt!