Automate dependency workflow further

[CasperWA]

In Materials-Consortia/optimade-gateway I have now succeeded in developing some workflows for automating the dependency handling further, automatically activating auto-merge for the @dependabot PRs, merging them into a permanent branch that's not the default branch and then once a week create a PR from this, generating a "burner" branch that's a copy of the permanent branch.
It's necessary with this "burner" branch due to the branch being automatically deleted upon merging.
Then when this special PR is merged the permanent dependency branch will be reset to the default branch.

As a note, I think I'd avoid including the providers updates in this system, as these updates should be merged into the default branch ASAP, while the dependency updates can (in theory) wait.

[ml-evs]

Sounds good to me! Bear in mind we still currently have to manually update the setup.py before merging the final PRs too.

[ml-evs]

Looks like my attempts at automating really fall down if changes are made to the default branch between deps updates (also if the deps branch is not properly reset with master), so your suggestions would be very welcome...

[CasperWA]

Sounds good to me! Bear in mind we still currently have to manually update the setup.py before merging the final PRs too.

Right. This needs to be either automated or restructured then. We should discuss this briefly in a video call I think.

[CasperWA]

Looks like my attempts at automating really fall down if changes are made to the default branch between deps updates (also if the deps branch is not properly reset with master) , so your suggestions would be very welcome...

Yeah. My solution was to keep merging the default branch (master) into the permanent dependency branch for every push to the default branch. And then reset it once the single dependency PR has been merged.