Introduce option for high volume request tracking

[rafaelroquetto]

Beyla tracks the full request completion time, this typically means we look to see if the application is responding with more data after the first HTTP response. One example would be a large file download, where the majority of the time is actually serializing the data on the wire. When the client uses keep-alive, we don't necessarily see the connection close event, but we tell by new pushed requests that we should terminate an earlier request.

This approach doesn't work well in when there's high volume of requests, e.g. beyond our current map sizing. The delayed requests will likely be booted out of the map before we have a chance to complete them. The ideal fix is to provide an option to resize the maps to match the volume of requests, but we need to finish the work of the tracer code restructuring for this to happen.

I'm adding an option to force Beyla to complete the request as soon as the response is finished. It will produce less accurate accounting for large file downlaods, but it will avoid no data for high volume of requests. We can also use this option to unblock clients if there are bugs in the delayed request accounting.

This PR is partial, since I accidentally pushed to main. Please review the following commits too:
7be9c33
and
bd3e5f4

(Original PR: #1192)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.10%. Comparing base (c3901b2) to head (dc5fba1).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1196      +/-   ##
==========================================
+ Coverage   81.03%   81.10%   +0.06%     
==========================================
  Files         136      136              
  Lines       11501    11501              
==========================================
+ Hits         9320     9328       +8     
+ Misses       1647     1641       -6     
+ Partials      534      532       -2     

Flag	Coverage Δ
integration-test	56.99% <ø> (+0.01%)	⬆️
k8s-integration-test	58.86% <ø> (+0.18%)	⬆️
oats-test	35.81% <ø> (ø)
unittests	53.30% <ø> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[grcevski]

LGTM!