Restrict false positive warning

[mpass99]

"Environment stopped unexpectedly," which also got triggered by migrations.

Related to #672

[codecov]

Codecov Report

Attention: Patch coverage is 35.29412% with 11 lines in your changes missing coverage. Please review.

Project coverage is 76.19%. Comparing base (b966aac) to head (f320878).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/runner/nomad_manager.go	35.29%	11 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #693      +/-   ##
==========================================
+ Coverage   76.14%   76.19%   +0.04%     
==========================================
  Files          43       43              
  Lines        3660     3676      +16     
==========================================
+ Hits         2787     2801      +14     
- Misses        636      640       +4     
+ Partials      237      235       -2     

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

[MrSerth]

Okay, let's give this a try. It seems like we are muting the alert if the environment returns within a minute, which should be enough time for any migration to finish.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ Environment stopped unexpectedly `` View Issue

_{Did you find this useful? React with a 👍 or 👎}

[MrSerth]

The issue occurred on our staging environment, which we heavily used to prepare the new CodeOcean environment. Hence, we can ignore this occurrence for now.