feat(aya): Add is_program_type_supported

[dave-tucker]

This adds a new API to test whether a given program type is supported.

This is to support 3 usecases:

1. A project like bpfman (which uses Aya) may wish to prevent users with a list of program types that are supported on the target system
2. A user of Aya may wish to test whether Fentry/Fexit programs are supported and code their own behaviour to fallback to Kprobes
3. Our own integration tests can be made to skip certain program tests when kernel features are missing.

---

This change is 

[netlify]

✅ Deploy Preview for aya-rs-docs ready!

Name	Link
🔨 Latest commit	7af8bf8
🔍 Latest deploy log	https://app.netlify.com/sites/aya-rs-docs/deploys/6793ca2d86e3e200087f6f1e
😎 Deploy Preview	https://deploy-preview-1145--aya-rs-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mergify]

Hey @alessandrod, this pull request changes the Aya Public API and requires your review.

[tyrone-wu]

Hi! I was wondering if #1063 could address the first usecase. I haven't updated it in a while, however last time I checked, program type and map type feature probing should be working correctly. I had planned to including another api for bpf_link_type probing along with bpf_attach_type, but I haven't had much time recently to work on it.

If it fits your first usecase, I can try to get my PR updated as soon as I can. :)

[dave-tucker]

Hi! I was wondering if #1063 could address the first usecase. I haven't updated it in a while, however last time I checked, program type and map type feature probing should be working correctly. I had planned to including another api for bpf_link_type probing along with bpf_attach_type, but I haven't had much time recently to work on it.

If it fits your first usecase, I can try to get my PR updated as soon as I can. :)

Here's the thing. This was just a quick hack to unblock #1135 and I totally forgot about your PR @tyrone-wu - sorry.
If you're up for it, let's do this.

1. I'll close this PR
2. You can Cherry-pick 6c3b2a6 and submit as it's own PR. It's mergeable pretty much immediately... and it reduces the diff making your other changes easier to review.
3. Rebase your remaining commits and mark it as ready for review so I can take a look. Having given it a quick glance I'm generally "ok" with it but I'd like to review it properly - I have questions that we may want to address in that PR, or as a follow up.

[tyrone-wu]

Srry for the delay. 😖

2. You can Cherry-pick 6c3b2a6 and submit as it's own PR. It's mergeable pretty much immediately... and it reduces the diff making your other changes easier to review.

That commit is now separated into #1162.

3. Rebase your remaining commits and mark it as ready for review so I can take a look. Having given it a quick glance I'm generally "ok" with it but I'd like to review it properly - I have questions that we may want to address in that PR, or as a follow up.

Just finished up some final testing for the remaining work, which should be updated in #1063. 👍

[dave-tucker]

Thanks so much @tyrone-wu!