ci: update performance test script for breaking Determined change

[NicholasBlaskey]

Description

We broke some Determined code we are using. This updates this to use the new session stuff.

Test Plan

Perf test passes

Commentary (optional)

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.

Ticket

[netlify]

✅ Deploy Preview for determined-ui canceled.

Name	Link
🔨 Latest commit	497ff74
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/65e87d0d30f8a40008368c27

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.37%. Comparing base (191a144) to head (497ff74).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8961      +/-   ##
==========================================
- Coverage   47.37%   47.37%   -0.01%     
==========================================
  Files        1162     1162              
  Lines      176134   176134              
  Branches     2237     2235       -2     
==========================================
- Hits        83448    83442       -6     
- Misses      92528    92534       +6     
  Partials      158      158              

Flag	Coverage Δ
backend	42.74% <ø> (-0.01%)	⬇️
harness	63.94% <ø> (-0.01%)	⬇️
web	42.54% <ø> (ø)

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

see 3 files with indirect coverage changes

[djanicekpach]

Looks good. I think the plan is to add a default password to deployments for security, so "" may not work at some point in the future.

[NicholasBlaskey]

Looks good. I think the plan is to add a default password to deployments for security, so "" may not work at some point in the future.

This work has already taken place.

This connects to a cluster running locally within the cirleci pod so there is no security issue.