chore(dependabot): enable updates with groups

[abn]

Summary by Sourcery

CI:

• Enable monthly grouped updates for pip dependencies.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request enables grouped updates in Dependabot configuration. This reduces PR noise by categorizing dependencies into production and development groups.

Flow diagram of Dependabot's new grouped update process

flowchart LR
    subgraph Monthly
        P[Production Dependencies] --> PG[Production Group PR]
        D[Development Dependencies] --> DG[Development Group PR]
    end
    subgraph Weekly
        E[Ecosystem Updates] --> S[Single PR]
    end

    style PG fill:#90EE90
    style DG fill:#90EE90
    style S fill:#ADD8E6

Loading

File-Level Changes

Change	Details	Files
Enabled grouped updates in Dependabot configuration.	Added a new configuration for pip dependencies. Configured monthly updates for pip dependencies. Added labels for pip dependencies. Configured groups for production and development dependencies. Set a limit of 2 open pull requests for pip dependencies.	.github/dependabot.yml

---

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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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]

Hey @abn - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[abn]

@sourcery-ai review

[sourcery-ai]

Hey @abn - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[radoering]

Do we really need separate PRs for prod and dev?

[abn]

Good question. I wanted to keep them separate to easily eye what priority any breakage needs. Because the dev deps causing issues, we can potentially defer solving by skipping updates. For main, it might already be causing issues for folks if there is an issue.