Pure GraphQL Peloton update script

[trexfeathers]

Uses GraphQL for both queries and mutations. This allows the inclusion of Discussions, and greatly reduced runtime.

Uses sgqlc for a Pythonic representation of GraphQL.

This is a big change. I recommend reading through the main() function of update_project.py to get a feel for the workflow, before diving into how the individual queries/mutations are constructed.

The Peloton in its current guise has been successfully populated by this script on several occasions, both locally and via GitHub Actions.

GitHub actions examples:

• Standard run: trexfeathers/SciTools.github 7184958408
• 5min looping run, via workflow dispatch: trexfeathers/SciTools.github 7185244488

Closes #14
Closes #12
Closes #11
Closes #10
Closes #9

[bjlittle]

@trexfeathers This is my first wave through, with only a few minor comments to service.

Pretty hard to get into, but I can see this code has been built up over a long period of time using graphql to query the repos. It's clear you've put a lot of effort into this, so thank-you 🍻

The structure looks good to me, with clean separation of concerns through your class hierarchy for non-mutable and mutable operations.

I'm keen to bank it so that we can all leverage it's benefit in the pelotons, and make course corrections as we go forwards 👍

[bjlittle]

@trexfeathers Awesome! Thanks for pushing this forwards, this'll make a huge difference to the peloton 🚀 🥳 🎉

[trexfeathers]

Thanks @bjlittle!

I'll give the workflow_dispatch a whirl and see if everything is working in the 'real world'