IWF-532: Close integration test workflows when finished

[lwolczynski]

Description

Checklist

• Code compiles correctly
• Tests for the changes have been added
• All tests passing
• This PR change is backwards-compatible
• This PR CONTAINS a (planned) breaking change (it is not backwards compatible)

Related Issue

Closes #537

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.80%. Comparing base (2d552b8) to head (bed4ac7).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #540      +/-   ##
==========================================
+ Coverage   64.66%   65.80%   +1.14%     
==========================================
  Files          59       62       +3     
  Lines        6639     6849     +210     
==========================================
+ Hits         4293     4507     +214     
+ Misses       2067     2063       -4     
  Partials      279      279              

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

[bowersj27]

LGTM. I think we should consider how we might effectively setup and teardown these integ tests' dependent environments in integ/util.go:dostartIwfServiceWithClient to achieve this in the future.

integ/util.go:dostartIwfServiceWithClient AFAICT sets up the iwf process and connection to the backing provider(cadence/temporal) for each test. We may be able to expand on this to track all started wf's and make sure they are closed on each test execution such that we don't have to explicitly add this behavior to each test in the future.

[lwolczynski]

LGTM. I think we should consider how we might effectively setup and teardown these integ tests' dependent environments in integ/util.go:dostartIwfServiceWithClient to achieve this in the future.

integ/util.go:dostartIwfServiceWithClient AFAICT sets up the iwf process and connection to the backing provider(cadence/temporal) for each test. We may be able to expand on this to track all started wf's and make sure they are closed on each test execution such that we don't have to explicitly add this behavior to each test in the future.

Opened #542 for it