chore(deps): update dependency certifi to v2026.7.22

[projecttickbot]

This MR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
certifi	==2026.4.22 → ==2026.7.22

---

Release Notes

certifi/python-certifi (certifi)

v2026.7.22

Compare Source

v2026.6.17

Compare Source

v2026.5.20

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Mend Renovate.

[projecttickbot]

✅ Danger review

All Danger checks passed.

⚠️ Warnings

• 1141ff4: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.
• This merge request does not have any assignee yet. Setting an assignee clarifies who needs to take action on the merge request at any given time.
• This merge request does not refer to an existing milestone.
• Please add a category label to this merge request so Foreman can route section/stage/group labels.
• Please add a changelog commit trailer to at least one commit. If a changelog entry is not needed, add any of the ~"documentation" labels.

We advise getting a review from GitLab Duo Code. You can assign @GitLabDuo as a reviewer to this merge request.

Reviewer roulette

Changes that require review have been detected! A merge request is normally
reviewed by both a reviewer and a maintainer in its primary category and by a
maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each
review slot. Feel free to
override these selections
if you think someone else would be better-suited
or use the GitLab Review Workload Dashboard
to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the
Engineering workflow
and code review guidelines.
Please consider assigning a reviewer or maintainer who is a
domain expert
in the area of the merge request.

Reviewer	Maintainer
No reviewer available	No maintainer available

Once you've decided who will review this merge request, mention them as you
normally would! Danger does not automatically notify them for you.

If needed, you can retry the 🔁 danger-review job that generated this comment.

[projecttickbot]

🚧 Test build enqueued.

[projecttickbot]

🚧 Build for master started.

Commit: afd09e3af637

[projecttickbot]

✅ Build for master succeeded.

⏱ Build duration: 41s.

[projecttickbot]

🚧 Test build enqueued.

[projecttickbot]

🚧 Build for master started.

Commit: 1141ff41ccc1

[projecttickbot]

✅ Build for master succeeded.

⏱ Build duration: 36s.