build: upgrade Gunicorn

[Nidhi091999]

resolve #174

Summary by Sourcery

Chores:

• Upgrade Gunicorn dependency to version 22.0.0 or higher.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades the Gunicorn dependency to version 22.0.0 in requirements.txt. This ensures that the application benefits from the latest features, security patches, and performance improvements in Gunicorn.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Upgraded the Gunicorn dependency to the latest version.	Updated the Gunicorn version from >=20.1.0,<21 to >=22.0.0.	requirements.txt

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#174	Upgrade the Gunicorn dependency to a version that addresses the security vulnerability GHSA-w3h3-4rj7-4ph4.	✅

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. We don't review packaging changes - Let us know if you'd like us to change this.

[uniqueg]

Thanks a lot @Nidhi091999: Do you want to try and address the linting and test issues (as well as the conflict)? I know it's not your changes that causes those, but I think the required changes are minor. You can do them in this PR or - even better - in another PR (to then be merged before this).

You can have a look at elixir-cloud-aai/cwl-WES#258 to get some inspiration on how to fix the test issues, I think the problem is the same (with docker compose vs. docker-compose - but it might require a couple more dependency upgrades).

[uniqueg]

Already addressed by #181 (Gunicorn upgrade) and #185 (for failing linting and tests)