740 update to new teaser use conditions and add new building elements

[DaJansenGit]

Before we can merge this, we need to

• merge Use pyproject.toml for everything and update test resources problem #732 to include the new test resources strategy
• merge dev into main and create a release. This is needed as the changes here will change the results of the simulations and we want to link a release with the current results in our paper
• update the templates in the new test resources repository to add the new attributes and add "version" entry in all templates
• Adjust the main plugin comfort templates that stay in the base repository.
  • cleanup comfort assets (move to test resources)
  • rename version 0.7 to TEASER-0.7
  • add new lighting parameters to comfort use conditions
• update reference results if we want to have the maintained_illuminance calculation as default (which I suggest due to much more realistic internal loads through lights)

Changes

• Thanks first to @HoeppJ for doing most of the changes. I needed to move them here to a fresh branch as there was some mixups with changes that are only related to your MA thesis.
• we now have updated use conditions with dynamic option to use use more realistic lighting power with the option to change the lighting efficiency (use LED efficiency instead old values that are all based on old lighting hardware with much higher consumption and therefore internal loads)
• support for newer building standards with KFW support
  • as for KFW we are not using building year, we can directly specify which type, e.g. by construction_class_walls= kfw_40
• next to IWU and KFW we also now have the tabula data building element data in bim2sim
• ...

This closes #740

[DaJansenGit]

Mir ist bei den Änderungen folgendes noch aufgefallen:

• lighting_power, bzw. jetzt fixed_lighting_power war für die Living use condition auf 7.0 statt 10.0 W/m² eingetragen beim file UseConditionsAC20-FZK-Haus.json. Dadurch würden sich die regression results ohnehin ändern, auch wenn
  use_maintained_illuminance nicht genutzt würde
• Multiple use conditions files for DigitalHub:
  • UseConditionsFM_ARC_DigitalHub_fixed002.json
  • UseConditionsFM_ARC_DigitalHub_with_SB89.json
  • UseConditionsFM_ARC_DigitalHub_with_SB_neu.json
  • Only one difference between the three files: cooling_profile for "Kitchen in non-residential buildings" during day is 297.15 K for with_SB89 and 294.15 K for the other two files.

--> As activating the use_maintained_illuminance will change reference results anyway, I deleted the redundant use conditions files for digital hub as the only changes between the files are SBs and space names there is no reason to have different use conditiosn files. Only customUsages files make sense. The new file UseConditionsFM_ARC_DigitalHub.json uses 297.15 K as we won't cool a residential kitchen with 300 W/m² due to internal load of machines to 21 °C.