Bump libseccomp to v2.5.5

[twz123]

Description

https://github.com/seccomp/libseccomp/releases/tag/v2.5.5

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist:

• My code follows the style guidelines of this project
• My commit messages are signed-off
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[juanluisvaladas]

Because what we mentioned before of merging dependencies I re run all the jobs.

Other than that LGTM

[twz123]

I plan to do a rebase, just to be sure.

[k0s-bot]

Successfully created backport PR for release-1.29:

• [Backport release-1.29] Bump libseccomp to v2.5.5 #3998