Bump the pip group across 1 directory with 15 updates

[dependabot]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[sentry]

Bug: The upgrade of gevent to 23.9.0 introduces an incompatibility with the older psycogreen 1.0.2, which can cause database operations to block the gevent event loop.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

The application uses psycogreen.gevent.patch_psycopg() to make database calls asynchronous. This pull request upgrades gevent to version 23.9.0 but leaves psycogreen at version 1.0.2, which was released in 2020. Due to the significant age difference and internal changes in gevent's event loop, this combination is not guaranteed to be compatible. This incompatibility could cause the patch_psycopg() call to fail or work incorrectly, leading to blocking database operations, deadlocks, or LoopExit errors at runtime.

💡 Suggested Fix

Upgrade psycogreen to a version that is officially compatible with gevent 23.9.0 or newer. Alternatively, investigate replacing psycogreen with a more modern patching library if one is available and better maintained.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: requirements.txt#L161-L173

Potential issue: The application uses `psycogreen.gevent.patch_psycopg()` to make
database calls asynchronous. This pull request upgrades `gevent` to version 23.9.0 but
leaves `psycogreen` at version 1.0.2, which was released in 2020. Due to the significant
age difference and internal changes in `gevent`'s event loop, this combination is not
guaranteed to be compatible. This incompatibility could cause the `patch_psycopg()` call
to fail or work incorrectly, leading to blocking database operations, deadlocks, or
`LoopExit` errors at runtime.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 7844269}