ResStock-HPXML: include_annual arguments

[joseph-robertson]

Support the following ReportSimulationOutput changes:

• A bunch of include_annual_foo are now available. We will fix (i.e., user has no option to override) requesting all annual outputs, except for system use consumptions which will always not be requested.
• Also fixes new include_timeseries_system_use_consumptions argument to always false.

[github-actions]

File	Coverage
All files	83%	✅
base.py	88%	✅
eagle.py	75%	✅
exc.py	57%	✅
local.py	50%	✅
postprocessing.py	84%	✅
utils.py	96%	✅
sampler/base.py	79%	✅
sampler/downselect.py	33%	✅
sampler/precomputed.py	93%	✅
sampler/residential_quota.py	61%	✅
test/test_docker.py	33%	✅
test/test_validation.py	97%	✅
workflow_generator/base.py	90%	✅
workflow_generator/commercial.py	53%	✅
workflow_generator/residential_hpxml.py	75%	✅

Minimum allowed coverage is 33%

Generated by 🐒 cobertura-action against 5e653dc

[nmerket]

Just pulling up the checklist from the pull request template...

• Code changes (must work)
• Tests exercising your feature/bug fix (check coverage report on Checks -> BuildStockBatch Tests -> Artifacts) Is it worth adding a simple test around this feature in the test_workflow_generator.py?
• Coverage has increased or at least not decreased. Update minimum_coverage in .github/workflows/ci.yml as necessary.
• All other unit and integration tests passing
• Update validation for project config yaml file changes
• Update existing documentation
• Run a small batch run on Eagle to make sure it all works if you made changes that will affect Eagle
• Add to the changelog_dev.rst file and propose migration text in the pull request

[joseph-robertson]

New test_workflow_generator.py checks are commented out because the test checks against resstock develop... but the new arguments aren't on develop yet...

[nmerket]

I think this is good. At what point do we merge this? Before or after the corresponding resstock change?

[joseph-robertson]

I think we merge here, then release buildstockbatch. Then I can go into the resstock PR and point to the tagged buildstockbatch release before merging it into develop. Does that sound right?