build(deps): bump junitparser from 4.0.2 to 5.0.0 in /ci/builder

[dependabot]

Bumps junitparser from 4.0.2 to 5.0.0.

Changelog

Sourced from junitparser's changelog.

[5.0.0] - 2026-03-28

Breaking

• Drop support for Python 3.9 and below. Use version 4 if you're still on an older Python version.
• Update type annotations thanks to @​nkr0
• Make TestCase support Properties tags thanks to @​eap

Commits

• 51b7f29 Merge branch 'master' of https://github.com/weiwei/junitparser
• 5950f59 release 5.0
• 35ec8d6 Make TestCase support Properties tags (#171)
• 8962ad3 Add type information in some places (#174)
• 154c4d4 Update sphinx requirement from ~=7.4 to ~=9.1 (#175)
• 94db4c0 Use newer license declaration format (#173)
• 689f9e1 Update LICENSE
• See full diff in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

• Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
• Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
• Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

• The PR title is descriptive and will make sense in the git log.
• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).