Template: Run awsfulltest after release, and with dev revision on PRs to master

[mirpedrol]

Close #3462

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 76.61%. Comparing base (f7207a5) to head (99db9e8).
Report is 9 commits behind head on dev.

Files with missing lines	Patch %	Lines
nf_core/pipelines/lint/actions_awsfulltest.py	50.00%	1 Missing ⚠️

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mashehu]

we can then remove the approval checking steps. they were anyway too buggy.

[mirpedrol]

we can then remove the approval checking steps. they were anyway too buggy.

If we remove this the tests will run two times, one when the first review is approved and submitted and one when the second one is submitted. Is this a no go? or we are fine with it?

[mashehu]

better then a wonky check before. but maybe we can check if there is already something in the S3 bucket and only run if it is empty or something like that?

[mirpedrol]

I have removed the check for now.
I am not sure how to check the S3 bucket, but I think it will give fewer errors if we override the content, in case there were some code changes.