[scapy] move the fuzz target upstream

[evverx]

as discussed in #12050

(It's a draft because I'm not sure if it's OK to move it and make the licence compatible with the repository. It would be great if someone could confirm that it's OK: secdev/scapy#4441)

[github-actions]

evverx has previously contributed to projects/scapy. The previous PR was #12074

[evverx]

I'll go ahead and close this since it hasn't been confirmed that it's OK to move the fuzz target.

On a somewhat related note having read https://security.googleblog.com/2024/06/hacking-for-defenders-approaches-to.html I'm kind of curious how all those patches and fuzz targets are going to be licensed.

[evverx]

Reopening in the hope that it can be approved in the end.

[evverx]

https://security.googleblog.com/2024/06/hacking-for-defenders-approaches-to.html

Speaking of AI I can remember an auto-generated patch that was on its way to reintroduce a remote DoS to systemd-resolved because that thing learned something on StackOverflow or something like that :-) I don't think the researchers published their paper in the end but "Validating the patches by running crashes and tests to ensure the crash was prevented and the functionality was not impacted" seems reasonable :-)