[Parse incomplete chunks 9/9] Add bpf test for loop limit exceeded

[benkilimnik]

Summary: Adds a bpf test for HTTP that triggers the gap condition LoopLimitExceeded based on a NodeJS application submitted in community slack. It submits an iovec with 257 elements, which is greater than our loop limit of 42. Our current behavior is that we merge 41 events into the data stream buffer, getting us to 878 bytes. Then on 42nd iov we reach loop limit, record the gap in metadata, and pad the rest with filler (or leave a gap if lazy parsing is enabled).

Type of change: /kind feature

Test Plan: Tested for both lazy and non-lazy HTTP parsing. Checked that metrics consistently show the loop limit exceeded condition for an iovec with length 257.