fix: ensure number of project keys possible for testing is not exceeded

[corban-beaird]

Ticket

Description

This reduces the number of requests being made by the TestConcurrentProjectKeyGenerationAttempts test to ensure we do not exceed the number of possible project keys given the project name, which was resulting in this test flaking.

Test Plan

• Ensure TestConcurrentProjectKeyGenerationAttempts passes

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	36a0b17
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/6668a1fc8976ff00087b6334

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 48.99%. Comparing base (de03909) to head (36a0b17).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9501   +/-   ##
=======================================
  Coverage   48.99%   48.99%           
=======================================
  Files        1235     1235           
  Lines      160191   160191           
  Branches     2780     2780           
=======================================
+ Hits        78482    78483    +1     
+ Misses      81534    81533    -1     
  Partials      175      175           

Flag	Coverage Δ
backend	43.82% <ø> (+<0.01%)	⬆️
harness	63.96% <ø> (ø)
web	44.12% <ø> (ø)

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

see 3 files with indirect coverage changes

[eecsliu]

looks good! Just one minor question

[eecsliu]

400 vs 5 is a huge difference...I doubt there will be so many concurrent keygens at once, but was there a requirement to handle any specific number of concurrent keygen attempts?

[corban-beaird]

Originally, I had wrote this to be a stress test to ensure that we could handle the case when we start to exhaust the set of project keys for a given project name pattern, but realistically I don't imagine we'll have folks creating 20 projects concurrently 20 times. It being able to support the creation of 5 project synchronously without issue is sufficient for the cadence we expect projects to be created.