Add selection of makerules and digital-land-python branch to dev/staging airflow environments

[CarlosCoelhoSL]

Overview

In the dev and staging environments on airflow, the current method to test out new changes involves redirecting the branch in the collection-task repo, and deploying that to dev/staging. This means that only one person can be testing out changes at a time, and every instance of dev/staging has to use those changes.

Instead we should have fields in airflow that allow the user to select the branch of digital-land-python and makerules that will be installed for that run, with the default being the main branch. This means that we don't have to update the whole dev/staging environment to test code changes.

Acceptance Criteria

• There exists 2 fields in the dev and staging environments, one for makerules and one for digital-land-python, that allow the user to select/type a branch name for the corresponding repos
• The default will be the main branch
• If the branch is typed manually, and doesn't exist, fail when trying to install makerules/digital-land-python (may or may not be possible)