feat: Add requestFinished event for per-request tracking

[shresthaoshan]

This pull request introduces a new requestFinished event to enable per-request tracking, complementing the existing socket-level tracking provided by the connectionClosed event. Implements #589

Key Changes:

• New requestFinished Event: The server now emits a requestFinished event upon the completion of a proxied request. This event provides granular details about each request, including its id, connectionId, and the original request object.
• Test: Added tests to test/server.js to ensure the requestFinished event is emitted reliably across various proxy configurations, including HTTP, HTTPS, and scenarios with upstream proxies.
• Example: Included a new example file, examples/request_finished.js, to demonstrate how to listen for and utilize the requestFinished event for monitoring purposes.

This enhancement provides more detailed visibility into individual requests flowing through the proxy, allowing for better logging and tracking.

[jirimoravcik]

Hello @shresthaoshan, I noticed that the tests are timing out, could you please take a look? Thanks

[oshanshrestha-grepsr]

Hello @shresthaoshan, I noticed that the tests are timing out, could you please take a look? Thanks

@jirimoravcik the tests seems to be already failing, even before this PR. Do you want me to look into it?