Regression Test git actions workflow

[amygutierrez]

Fixes

Automate regression testing whenever there's a pull request ready to review and whenever there is a merge to main from develop.
Fixes #1904 by @amygutierrez

Description

This workflow will automate regression testing for CPAC.
The repo reg-suite can be run with 2 different options: --lite and --full.
--lite
This will use downsampled datasets stored in OSF.

Technical details

Tests

Screenshots

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the develop branch of the repository.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added tests for the changes I made (if applicable).
• I updated the changelog.
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[shnizzedy]

[shnizzedy]

I set up an environment for running on ACCESS
, and we can apply it by including environment: ACCESS in any jobs where we want these rules to apply like

Suggested change

	runs-on: ubuntu-latest
	steps:
	runs-on: ubuntu-latest
	environment: ACCESS
	steps:

I set "Allow administrators to bypass configured protection rules" to true; that's what we want, right?

[shnizzedy]

I'm working on this in my forks shnizzedy/C-PAC@regression/reg-suite & shnizzedy/slurm_testing@regression/after_runs so there aren't a bunch of test CI runs going on FCP-INDI