Add KDS Workflows to keep KDS Roadmap statuses updated

[AlexVelezLl]

Description

Adds two workflows to keep KDS Roadmap statuses updated:

1. Sync KDS Roadmap Project Statuses: Sets up a cronjob to keep KDS Roadmap project statuses synced with the Iteration backlog project items status.
2. Update KDS Roadmap project statuses on Release: When we have a new kds release, this workflow will check all released PRs and will set their statuses to Released and will update the released in field to the release version.

Changelog

• Description: Adds Adds two workflows to keep KDS Roadmap statuses updated
• Products impact: none.
• Addresses: -.
• Components: -.
• Breaking: no
• Impacts a11y: no
• Guidance: -.

Steps to test

I have tested these actions in the https://github.com/learningequality/test-actions repo. We can dispatch:

• https://github.com/learningequality/test-actions/actions/workflows/sync_kds_roadmap_statuses.yml: For this, we will need to go to the KDS Roadmap project and simulate a situation where we have an updated status in the Iteration Backlog, but not in the KDS Roadmap project.
• https://github.com/learningequality/test-actions/actions/workflows/update_project_items_on_release.yml: For this, we will need to simulate a release adding to the context input an object like this:
  { "payload": { "action": "published", "release": { "body": "Some release notes https://github.com/learningequality/kolibri-design-system/pull/783", "name": "v0.0.1"}, "repository": { "name": "kolibri-design-system", "owner": { "login": "learningequality" } } }, "eventName": "release"}

[rtibbles]

I always wish there was a nicer way to construct GraphQL queries than creating a string template - but that seems to be the preferred way.

As you've tested this elsewhere, I think there's no much point holding this up, so we should just merge, let it run, and make sure it's doing what it ought!

[rtibbles]

I think these might be better encoded as org and repo secrets.

[rtibbles]

Oh, sorry - actually let's move the ids into secrets that we read in the workflow and then pass into the JS functions.

[AlexVelezLl]

Thanks @rtibbles! I've pushed the requeseted changes :)

[rtibbles]

Secrets added at the org level and exposed to the KDS repo.

[MisRob]

@AlexVelezLl @rtibbles

@EshaanAgg noted #906 - would it be possible to limit the action run to LE repo only?