Upgrade the instances

[geoffreyvanwyk]

Basically, a schedule should be added to the Deploy workflow for running once a week.

The workflow should run on the hour and disable the Reset workflow before starting, then reenable it afterwards.

[geoffreyvanwyk]

Moodle releases major versions (x.y, e.g. 4.1) every six months in April and October, minor versions (x.y.z) every two months. These are indicated with tags in the Moodle Git repository. See https://moodledev.io/general/releases#general-release-calendar

Learning Sandbox Online should be based on these releases and not simply on the code in the stable branches. The Ansible playbook should set the versions for the Git module for each Moodle instance to the relevant tag instead of the stable Moodle branch. To upgrade, the tag should just be updated every two months and then the Deploy workflow should be run.

[geoffreyvanwyk]

This is going to be a recurring manual task for now. The first iteration will be taken care of by #56 . This task can be closed.

[geoffreyvanwyk]

It could be implemented as a scheduled GitHub Actions workflow that checks for new Moodle tags every two months. When it finds a new tag, it runs the Deploy GitHub Actions workflow with the new tags as input. That means the Deploy workflow must be modified to take tags as input.