Feature 562 export storage units

[nesnoj]

Summary of the discussion

Allows CSV export of table storage_units

• db.to_csv() and db.to_csv("storage_units") now export to bnetza_mastr_storage_units_raw.csv.
• db.download("bulk", data="storage") does not include storage_units/anlagenstromspeicher anymore as I had to split "storage" in BULK_INCLUDE_TABLES_MAP to allow for CSV export. Instead, if a user wants only the storage units to be written to the DB, they need to be written separately via db.download("bulk", data="storage_units"). I assume most users write all data to the DB anyways (db.download("bulk")) which works properly.

Updated

• Allow CSV export of table storage_units #562

Workflow checklist

Automation

Closes #562

PR-Assignee

• 🐙 Follow the workflow in CONTRIBUTING.md
• 📝 Update the CHANGELOG.md
• 📙 Update the documentation

Reviewer

• 🐙 Follow the Reviewer Guidelines
• 🐙 Provided feedback and show sufficient appreciation for the work done

[nesnoj]

Oh, discovered a bug in my implementation, will check..

[nesnoj]

Ok, good to go now

[FlorianK13]

There is the problem of tests not running. This happens when:

• All files are pushed to a draft PR (changes to a branch with a draft PR do not trigger tests)
• The draft PR is converted to a normal PR (changing this status does not trigger tests)

I just checked but I could find no way to run the tests manually on this PR. @nesnoj do you know this problem and a solution? The only solution that I know is to add a small change and push it to the feature branch, which will trigger the tests.

[nesnoj]

Ok, did some minor "fix" to trigger ;)

Thanks for the explanation @FlorianK13 !
This is quite weird, maybe the trigger ready_for_review could do the trick..

BTW, the if statement in the test if: ${{ !github.event.pull_request.draft }} is not required to my mind as tests should not be triggered in draft PRs by default.