chore(deps, cpp): update udev, xsltproc

[Ron (rjaegers)]

🚀 Hey, I have created a Pull Request

Description of changes

This PR updates udev and xsltproc to the latest version. This is a manual action since the package sources have been changed and no release has been made yet. This means that the 'latest' version that is used in the package update workflows does not yet include the changed package source.

✔️ Checklist

• I have followed the contribution guidelines for this repository
• I have added tests for new behavior, and have not broken any existing tests
• I have added or updated relevant documentation
• I have verified that all added components are accounted for in the SBOM

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	17		0	0.06s
✅ DOCKERFILE	hadolint	2		0	0.51s
✅ GHERKIN	gherkin-lint	2		0	0.88s
✅ JSON	npm-package-json-lint	yes		no	0.35s
✅ JSON	prettier	15	1	0	0.35s
✅ JSON	v8r	15		0	8.9s
✅ MARKDOWN	markdownlint	8	0	0	0.88s
✅ MARKDOWN	markdown-table-formatter	8	0	0	0.25s
✅ REPOSITORY	checkov	yes		no	15.48s
✅ REPOSITORY	gitleaks	yes		no	0.92s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	10.35s
✅ REPOSITORY	secretlint	yes		no	1.03s
✅ REPOSITORY	syft	yes		no	1.39s
✅ REPOSITORY	trivy	yes		no	5.15s
✅ REPOSITORY	trivy-sbom	yes		no	0.09s
✅ REPOSITORY	trufflehog	yes		no	3.08s
✅ SPELL	lychee	59		0	1.21s
✅ YAML	prettier	22	0	0	0.76s
✅ YAML	v8r	22		0	6.09s
✅ YAML	yamllint	22		0	0.4s

See detailed report in MegaLinter reports

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

• oxsecurity/megalinter/flavors/dotnet@v8.4.2 (61 linters)
• oxsecurity/megalinter/flavors/dotnetweb@v8.4.2 (70 linters)

[github-actions]

Test Results

 2 files  ±0   2 suites  ±0   1m 18s ⏱️ -3s
29 tests ±0  29 ✅ ±0  0 💤 ±0  0 ❌ ±0 
31 runs  ±0  31 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 2949851. ± Comparison against base commit 39e2f85.

♻️ This comment has been updated with latest results.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Compressed layer size comparison

Comparing ghcr.io/philips-software/amp-devcontainer-rust:latest to ghcr.io/philips-software/amp-devcontainer-rust@sha256:04f6cebbd548a891b200aae13f5348a4fbb177618b694ba4fcec1b147c2b3236

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	484.88M	484.88M	5.44K (+0.00%)
linux/arm64	623.73M	623.73M	5.00K (+0.00%)

[github-actions]

Compressed layer size comparison

Comparing ghcr.io/philips-software/amp-devcontainer-cpp:latest to ghcr.io/philips-software/amp-devcontainer-cpp@sha256:c99e1e1504226528f26811befa286edcef89ac1039e1521c3727ff933ec7f339

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	697.85M	701.52M	3.68M (+0.53%)
linux/arm64	679.20M	683.23M	4.04M (+0.59%)

[github-actions]

Pull Request Report (#751)

Static measures

Description	Value
Number of added lines	2
Number of deleted lines	2
Number of changed files	1
Number of commits	2
Number of reviews	1
Number of comments (w/o review comments)	5
Number of reviews that contains a comment to resolve	0
Number of reviews that requested a change from the author	0
Number of reviews that approved the Pull Request	1
Get the total number of participants of a Pull Request	4

Time related measures

Description	Value
PR lead time (from creation to close of PR)	6.3 Hours
Time that was spend on the branch before the PR was created	23 Sec
Time that was spend on the branch before the PR was merged	6.3 Hours
Time to merge after last review	6.2 Hours

Status check related measures

Description	Value
Total runtime for last status check run (Workflow for PR)	3.6 Hours
Total time spend in last status check run on PR	3.1 Hours

[github-actions]

🎉 Hooray! The changes in this pull request went live with the release of v5.7.0 🎉