Split core eBPF and network extension tests.

Separating the CICD pipelines for core eBPF and network extension would improve engineering agility.

There are a few steps required to achieve this:

- separate all eBPF core and netebpfext tests. Currently, there are unified unit tests, driver tests and stress tests. There must be 2 separate set of tests for eBPF core and netebpfext.
- Many of the tests for core eBPF features (such as maps, tail calls) use test programs of type bind etc. that are dependent on the network extensions. All such tests need to be moved the sample extension.