Init a seccomp project

[utam0k]

This is an experimental crate. I'll implement a seccomp crate step-by-step.
When it is mature, I'll move it under the crate/ and use it instead of libseccomp.

ref: #2724

[codecov-commenter]

Codecov Report

Merging #2729 (3266094) into main (ed2c08d) will not change coverage.
Report is 28 commits behind head on main.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2729   +/-   ##
=======================================
  Coverage   65.21%   65.21%           
=======================================
  Files         133      133           
  Lines       16981    16981           
=======================================
  Hits        11074    11074           
  Misses       5907     5907           

[YJDoc2]

I'll try to take a look at this later today 👍

[YJDoc2]

Hey, great as a starting point! I have left some comments, which we might want to consider, but we can consider them in later commits, this is good to go, so approving.

Also, eventually when we have enough of lib ready, we should consider portin https://github.com/seccomp/libseccomp/tree/main/tests tests over here, so we can validate our impl. I think in their CI they compile and link these tests against branch build, which in case of rust is similar to unit tests, so we should be able to use those examples as part of crate/top level unit tests.

[YJDoc2]

@utam0k Should I go ahead and merge this?

[utam0k]

@utam0k Should I go ahead and merge this?

Thanks for your review. I'll fix them on this PR

[utam0k]

@YJDoc2 Do you want to take another look?

[YJDoc2]

lgtm 👍

Can merge once the CI is done 👍

[utam0k]

@YJDoc2 Thanks for your quick review 😍