Allow acceptable result ranges for integration tests

[MGibson1]

Type of change

- [ ] Bug fix
- [ ] New feature development
- [x] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

I've had issues with this test https://github.com/bitwarden/server/runs/15556068099#r6. It seems to me like what we're really interested in is blocking requests at about this frequency, and slightly faster or slower is OK.

I also changed the number of requests. Comments says it's limited to 10/sec. It seemed like 10 requests was a safer value

Before you submit

• Please check for formatting errors (dotnet format --verify-no-changes) (required)
• If making database changes - make sure you also update Entity Framework queries and/or migrations
• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team

[bitwarden-bot]

Checkmarx One – Scan Summary & Details – f50ca2b2-a1eb-419c-96cd-0ee47f089b0c

No New Or Fixed Issues Found

[nsbgit]

LGTM