Schedule CSV Generation

[ibrahimjaved12]

What are the relevant tickets?

Closes https://github.com/mitodl/hq/issues/3326

Description (What does it do?)

This PR adds a Github Action which creates a weekly Release with the newly created CSV file.
If this step fails: poetry run python -m ocw_oer_export.cli --create_csv --output_path="./private/output/ocw_oer_export.csv"

Then it creates a Slack alert for the notifications-ocw-oer-export channel, such as this:

Although the event would be schedule or push, not pull_request (that was for testing purposes).

All the releases would be found here: https://github.com/mitodl/ocw_oer_export/releases
The latest release would be found on this URL: https://github.com/mitodl/ocw_oer_export/releases/tag/latest

The release tags follow the semversioning pattern:
vx.y.z-csv (where z would be incremented every week).
Eg. v1.0.1-csv, v1.0.2-csv.

How can this be tested?

Feel free to produce errors on this PR as commit and then check for Slack notifications. You can also check from the error I produced (from the commits) and its Slack notification (Check the existing Actions on the repo)

The steps to run the program are same as before, but that won't test the Github Actions.

1. Checkout to this branch
2. Build the container:

docker compose build

3. Start the container:

docker compose run --rm app

4. To generate a JSON file containing complete API data:

docker compose run --rm app --create_json

5. To create a CSV file from the local JSON file:

docker compose run --rm app --create_csv --source=json

6. To run unit tests:

docker run --rm ocw_oer_export python -m unittest discover

[ibrahimjaved12]

@gumaerc The README.md will also have to be updated after this. I'll do it afterwards we establish that we're good to go with the current approach. I might update it in the other, trivial OCW OER Export PR I'm working on - to reduce the number of PRs to review.

[gumaerc]

👍

I tested this locally using [act](https://github.com/nektos/act) and it successfully generated a CSV. It failed when it went to create the release with:

| Creating release: v1.0.3-csv
| /var/run/act/workflow/9: line 3: gh: command not found

... but I think it's just an issue with act itself.