chore: fix a few flaky CSOT tests

[baileympearson]

Description

What is changing?

I've noticed a number of flaky CSOT tests. This PR attempts to fix the flakiness.

Is there new documentation needed for these changes?

What is the motivation for this change?

Release Highlight

Fill in title or leave empty for no highlight

Double check the following

• Ran npm run check:lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[nbbeeken]

                             Client Bulk Write
[2024/10/15 16:20:50.617]        CSOT enabled
[2024/10/15 16:20:50.617]          acknowledged writes
[2024/10/15 16:20:50.617]            when the timeout is reached while iterating the result cursor
[2024/10/15 16:20:50.617]              the bulk write operation times out:
[2024/10/15 16:20:50.617]      AssertionError: expected 1499 to be within 1500..2300

off by 1! should we expand the range?

[baileympearson]

evergreen retry

[baileympearson]

#4278 (comment)

That's not behavior I'd ever expect - the killCursors is so slow that it usually takes an extra 5-7 hundred ms. I think we should leave this as-is, and if it continues to flake we should look into why it runs so much more quickly sometimes. That might be a bug in our CSOT logic.

[nbbeeken]

SGTM, just seeing if I can clear the flakes, but will merge soon.