Implement phase 1 of new HTTP API (PoC)

[imiric]

See the specification in the design document.

---

amended by @oleiade on the 30th of November 2023

The maintainers' team agreed upon the following concrete plan to move forward with the implementation of the new HTTP module's phase 1 (as specified in the design document):

Tasks

Preview Give feedback

1. Begin with the implementation of the Streams API.
2. Agree upon most minimal scope for the new HTTP module's client API implementation, as per design document.
3. Implement 👆scope, with a focus on enabling the use of large binary files, leveraging the Streams API, and likely providing a native implementation of FileData

Specifically out of scope for phase 1:
The maintainers agreed that support for TCP, DNS, etc, should be delegated to a future phase.

edit, 30/10/2023: edited the original issue description with a task list based on internal discussion. I had to edit the description to attach a tasklist to this issue.

[saniyar-dev]

Hi, everyone. I'm currently working on this issue by implementing the phase 1 of this new HTTP API in this repo, in form of an k6 extension. i worked hours on it, still need to implement lots of features to it. I would be very thankful to anyone who wants to share their insights on it with me.
Also i know that it needs a lot of progress to be a candidate for a standard implementation of phase 1 for the new HTTP API, but can anyone share any roadmap, etc. to help me find my way through it? Any contact point to reach and talk with the team would be great too!
I'm getting confused as there is lots of open issues with this label however i read lots of them and i think i can implement all.