feat: Add request path to response entries

[NivLipetz]

Adds the request path to each response entry. This feature is useful when looking at the test as a whole, or at periods of time, to narrow down which requests returned 2xx/4xx/5xx as well as their latencies. This enhancement of metrics allows for better understanding of each endpoint the test loads.

[hassy]

This could be done with a custom afterResponse JS function rather than by extending the internal stats object. Any reason that wouldn't work for your use-case?

[NivLipetz]

For my use-case it doesn't seem that I can recreate my needed behaviour by only using the afterResponse JS function.

The motivation of this feature is to be able to audit the number of requests sent and response codes received from each distinct endpoint. This can only be done by adding the path to each entry as done in the file /core/lib/runner.js where the event response is listened to.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}