Update pyproject.toml

[yaxit24]

Here the updated configuration is ready for uv to manage dependencies.
Production libraries remain in the main dependencies list, while development tools have been moved from the dev feature (in [project.optional-dependencies]) into a dedicated dependency group ([project.dependency-groups.dev]). This separation is what uv (and modern practices) recommend.

here please let me know for any further changes and correction made, Also being new to open source, please suggest me with projects and issues to contribute.

Summary by Sourcery

Enhancements:

• Separates development dependencies into a dedicated dependency group.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request refactors the pyproject.toml file to improve dependency management and readability. It moves development dependencies into a dedicated dependency group and updates the file's formatting.

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

File-Level Changes

Change	Details	Files
Moved development dependencies from project.optional-dependencies to project.dependency-groups.dev. This aligns with modern practices and uv's recommendations for managing dependencies.	Removed the dev group from project.optional-dependencies. Created a new dependency group project.dependency-groups.dev. Added development-related packages to the project.dependency-groups.dev group, including django-debug-toolbar, pycodestyle, pyflakes, flake8, pep8-naming, coveralls, coverage, pytest, and others.	pyproject.toml
Updated the formatting and styling of the pyproject.toml file for improved readability and consistency.	Replaced double quotes with single quotes for string values. Added trailing commas to lists of dependencies and authors. Reformatted the authors and maintainers sections to improve readability. Added spaces around operators and after commas for better visual clarity.	pyproject.toml

---

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.

[hongquan]

Please add the link to the original issue.

[hongquan]

I updated the requirements for the dependency-group in #571.

[yaxit24]

please review #576

[hongquan]

@yaxit24 New changes should be added up here, not creating another PR.