feat: use composite actions for python scripts

[mariajgrimaldi]

Description

This PR is a continuation of a proposal I made here about making scripts more maintainable in the long term. I mentioned I had to figure out a good way of calling scripts within our workflow. Here's what I came up with:

Python scripts hosted in .github/workflows/actions

The additional functionalities with complex logic for the workflow should be implemented in a Python script hosted in a subdirectory within .github/workflows/actions with an explicit name containing its purpose. In this case, the script gets tutor configuration values, so the folder is called get-tutor-config, just like the Python script. Each script should be well-documented and modular, have a single responsibility, and be able to be executed locally for easier debugging.

Composite actions running Python scripts

• Create a composite action that executes the script with the necessary configurations:
• Call the composite action in the reusable workflow instead of the hardcoded script:

For this setup to work, we'd have to modify the workflow by:

I consider this approach to be more maintainable since we can now easily lint, test, and debug scripts. However, I understand it adds more layers of complexity, although easy to implement and use. The composite actions within .github/workflows/actions are meant to be small and straightforward since the only code added is a shell script executing a Python script. Therefore, the Python script should handle all complex logic to avoid returning to our previous situation.

This implementation is not set in stone, so feedback is very welcome.