ci(dependabot-pip): bump pycparser from 2.22 to 3.0 (SRV-128)

[dependabot]

Bumps pycparser from 2.22 to 3.0.

Release notes

Sourced from pycparser's releases.

release_v3.00

What's Changed

• Removed dependency on PLY, by rewriting pycparser to use a hand-written lexer and recursive-descent parser for C. No API changes / functionality changes intended - the same AST is produced.
• Add support for Python 3.14 and drop EOL 3.8 by @​hugovk in eliben/pycparser#581
• Update _ast_gen.py to be in sync with c_ast.py by @​simonlindholm in eliben/pycparser#582

Full Changelog: eliben/pycparser@release_v2.23...release_v3.00

release_v2.23

What's Changed

• Allow abstract declarator "static" (GH issue #539) by @​gperciva in eliben/pycparser#545
• Add support for Python 3.13 by @​hugovk in eliben/pycparser#550
• Add dirent and socket typedefs. by @​MegaManSec in eliben/pycparser#558
• Support for labels with no statement by @​ignatirabo in eliben/pycparser#562
• Accept empty 'case' or 'default' labels by @​ignatirabo in eliben/pycparser#564
• fix: preserve parentheses for statement exprs by @​zawan-ila in eliben/pycparser#566
• fix: hex float types by @​zawan-ila in eliben/pycparser#567
• Explicit error for comments, with README link by @​cellularmitosis in eliben/pycparser#569
• showemptyattrs option on Node.show() by @​cellularmitosis in eliben/pycparser#570
• Add fake typedefs for GNU Extension 128-bit integers. by @​dj-wednesday in eliben/pycparser#577
• Typedef for __kernel_sa_family_t in linux/socket.h by @​crosser in eliben/pycparser#578

New Contributors

• @​gperciva made their first contribution in eliben/pycparser#545
• @​MegaManSec made their first contribution in eliben/pycparser#558
• @​ignatirabo made their first contribution in eliben/pycparser#562
• @​zawan-ila made their first contribution in eliben/pycparser#566
• @​cellularmitosis made their first contribution in eliben/pycparser#569
• @​dj-wednesday made their first contribution in eliben/pycparser#577
• @​crosser made their first contribution in eliben/pycparser#578

Full Changelog: eliben/pycparser@release_v2.22...release_v2.23

Commits

• 77de509 Prepare for release 3.00
• e57ccd1 Update README
• 230e12d disable uv caching in CI
• 9c52f40 Update CI to run make check+test via uvx
• 6b8f064 Use dataclass where applicable; add 'make test' to Makefile
• 25376cb Use f-strings instead of older formatting in other auxiliary files
• 9bd8997 Use f-strings instead of older formatting in core code + tests
• 664eac2 Modernize some code with pattern matching
• 842f064 Add type annotations to more examples
• 076f374 Add types to several exmaples
• Additional commits viewable 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]

	Warnings
⚠️	The source branch "dependabot/pip/pycparser-3.0" incorrect format: contains more than one slash (/). This can cause troubles with git sync. Please rename your branch.

👋 Hello dependabot[bot], we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 970fd27

[dependabot]

Looks like pycparser is up-to-date now, so this is no longer needed.