ci: don't run test-e2e-longrunning tests on main

[NicholasBlaskey]

Ticket

Description

test-e2e workflows will already have them. test-e2e-longrunning is pure duplication on main.

Test Plan

See if main is still running these after this lands

Checklist

• Changes have been manually QA'd
• User-facing API changes need the "User-facing API Change" label.
• Release notes should be added as a separate file under docs/release-notes/.
  See Release Note for details.
• Licenses should be included for new code which was copied and/or modified from any external code.

[netlify]

✅ Deploy Preview for determined-ui canceled.

Name	Link
🔨 Latest commit	f5d3fbd
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/66391749fc74bc00083e9045

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.63%. Comparing base (9cab46d) to head (f5d3fbd).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9313   +/-   ##
=======================================
  Coverage   44.63%   44.63%           
=======================================
  Files        1275     1275           
  Lines      156285   156285           
  Branches     2449     2449           
=======================================
+ Hits        69756    69757    +1     
+ Misses      86289    86288    -1     
  Partials      240      240           

Flag	Coverage Δ
backend	41.82% <ø> (+<0.01%)	⬆️
harness	64.09% <ø> (-0.01%)	⬇️
web	35.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 5 files with indirect coverage changes

[davidfluck-hpe]

Looks good. Just a quick question to verify, though: the PR title/description talk about not running these specific tests on main, but the filter anchor also includes /pull\/.*/ and /release-.*/ regexes. Is that desired?

[NicholasBlaskey]

Looks good. Just a quick question to verify, though: the PR title/description talk about not running these specific tests on main, but the filter anchor also includes /pull\/.*/ and /release-.*/ regexes. Is that desired?

Yeah most other tests follow this pattern. The ones that weren't gated to *upstream-feature-branch are an exception. If we do want to change how the release runs test it should be all of them.

[davidfluck-hpe]

Ah, I see. Thanks!