This is a test of GitLab CI that prints the default python3 version.

Let non-Staff (e.g. Admin) do batch determination

See merge request !56

When an Admin who otherwise could make determinations on submissions
does a batch determination then it should succeed. This commit allows
it to succeed or throws a permissions error otherwise.

Issue ots/clients/ardc/hypha-tracker#271: Batch determination fails
    with 500 error

Fix error where default send being off canceled all messages

See merge request !55

If default send is off for slack or email, then even if messages were
configured to send, they weren't getting sent.  Instead, it needs to
always use the message setting if available, and only rely on default
send if not.

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

Merge 5.3.1

See merge request !54

Related to work done on ots/clients/ardc/hypha-tracker#219: Permit the
storing and viewing of contracts in the Projects section

Add wagtail configuration for messaging

See merge request !53

These are taken care of via the wagtail settings now, and don't need to
be handled in code.

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

These are taken care of via the wagtail settings now.

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

This is not all of them, but a good representation for how to use the
variables.  When upstreaming, we may want to build out more, but that
will require a conversation with upstream about how to go about changing
the message generation.

For a large number of the messages, there's non trivial business logic
in either the messages or the generation of them that needs to be moved
out or handled in another way.

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

This will all be repalced by configuration!!

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

This uses those settings in the following places:
* Message setting
* Whether an email/slack should be sent
* Subject setting

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

This doesn't build out any of the default messages (that comes later),
but sets the stage for it.

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

This sets up the rest of changes coming and needed.

Issue ots/clients/ardc/hypha-tracker#218:  Permit outgoing
messages/notifications to be configured in Wagtail

Fix regression where saving as draft submitted the application

See merge request !52

Add Wagtail setting to skip vendor contract upload

See merge request !50

Hypha tracks whether a contract has been signed and countersigned
depending on which role uploaded it and the context of the upload.
This change creates a new Wagtail setting called
`upload_countersigned_contract`. When set to `True`, whenever a
contract upload occurs, the UI shows that the document needs to be
countersigned and the document gets marked as countersigned. The net
effect is that there is no need for two contract uploads, only one.
When combined with the `staff_upload_contract` set to `True`, staff
can upload a single contract document without other users' actions.

Issue ots/clients/ardc/hypha-tracker#219: Permit the Staff/Staff Admin
    roles to upload contracts.

To make it easier for administrators to change the Project workflow,
change the low-level setting `STAFF_UPLOAD_CONTRACT` into a Wagtail
Project Setting `staff_upload_contract`.

Issue ots/clients/ardc/hypha-tracker#219: Permit the Staff/Staff
    roles to upload contracts.

Gracefully handle no configured report form case

See merge request !51