Problem

In a recent maintainer retrospective, we discussed that it was sometimes hard to get an understanding of the daily activity in the project. This made it hard for everyone to understand clearly what the priorities were and how their work fits into them.

Description

Create a new JavaScript automation that generates a daily status update. Print this in the GitHub action logs and also send it to a new Slack channel named openverse-daily.

The output format should be something along these lines:

Newly assigned todos:
  - @<openverse maintainer> assigned to #123, #124, #125
  - ...

Injected todos:
  - @<openverse maintainer> added #542

<OR>

Injected todos:
  - None! Awesome!

Newly in progress:
  - @<openverse maintainer> moved #126, #174 in progress

Newly blocked:
  - #1254: Fix the blah blah blah
  - #1235: Add new blah blah blah

Still blocked:
  - #1245: omg how do we fix this scary bug :scream: :ghost: :bug:

Needs review:
  - <all items that need review, sorted by priority/urgency>

Closed since yesterday :tadaco::
  - @<openverse maintainer> closed #421: Amazing new feature!
  - @<another openverse maintainer> closed #532: Whoa, what a sweet bug fix!
  - ...

Additional context

A JavaScript automation run as a GitHub action cron job is preferable (in fact, required, with our current infrastructure) to an Airflow DAG because GitHub projects v2 are only accessible via GraphQL and @octokit/rest is the easiest way to interact with that API. We also have existing project automations in JavaScript and there could be potential code-sharing opportunities.

Marked as staff only due to access requirements.