✅ Verify successful build of Nipype graphs for each config

[shnizzedy]

Related problem

We currently only run these smoke tests by explicitly running them when the CI could run them all for us every time!

Proposed feature

For each packaged preconfig, run test_config for each test subject.

Knock out FCP-INDI/C-PAC#1680 first to keep the list of packaged preconfigs always current

Acceptance criteria

• CI runs test_config for each test subject on PR

Alternatives

No response

Additional context

These run, but there's so many it takes a long time (see #7: Proposed Feature), so I think we should:

1. Just run a small handful (1 ‒ 3) of smoke tests on open PRs to `develop`

2. Run the full suite of smoke tests on pushes / successful merges to `develop`

3. Run the full suite of smoke tests on open PRs to `main`

― @shnizzedy, #3 (comment)

[shnizzedy]

These run, but there's so many it takes a long time (see #7: Proposed Feature), so I think we should:

1. Just run a small handful (1 ‒ 3) of smoke tests on open PRs to develop
2. Run the full suite of smoke tests on pushes / successful merges to develop
3. Run the full suite of smoke tests on open PRs to main

[shnizzedy]

1 sub per dataset, only on main image

― CNL Weekly Meetings 06/09/2022: smoke tests

[shnizzedy]

Deprecated by #1842