add optional stream to command

[alexcos20]

Changes proposed in this PR:

• add optional stream to command

• see https://github.com/oceanprotocol/ocean-node/pull/1318/changes#diff-30415eac87661d5c5d2e35045969efec41f8655a3e05ce130056c533ce77a902

[alexcos20]

/run-security-scan

[alexcos20]

AI automated code review (Gemini 3).

Overall risk: medium

Summary:
This pull request introduces the capability to send request bodies as a stream (P2PRequestBodyStream) through the P2P provider, aligning with the p2pStreamBody mechanism in ocean-node. This enables true streaming uploads, preventing the need to buffer entire request bodies in memory for large data transfers. The changes include adding new types and helper functions for stream handling, modifying dialAndStream and send methods to accept and process the request body stream, and updating the CI workflow to run on all branches.

Comments:
• [INFO][other] Changing branches to ** will run CI on all branches. This is fine for PRs, but be mindful of potential increased CI usage/costs if this also applies to pushes on many feature branches not intended for immediate merge.
• [INFO][other] The P2PRequestBodyStream type definition is clear and well-suited for handling various chunk types, ensuring flexibility for consumers of this API.
• [INFO][other] The toUint8ArrayChunk utility function correctly handles different input types (Uint8Array, string, ArrayBufferView) for conversion, making the stream processing robust.
• [INFO][other] The writeP2pRequestBodyLp function correctly implements the logic for streaming the body and terminating with an empty LP frame, which is crucial for interoperability with ocean-node's p2pStreamBody mechanism.
• [INFO][other] Adding p2pStreamBody: true to the initial payload when a request body stream is present is a good way to signal to the receiving ocean-node that a stream will follow, enabling proper parsing on their end. This ensures protocol compatibility.
• [ERROR][other] There are no tests included for this significant new streaming capability. Introducing streaming functionality, especially in a networking context, can have various edge cases (e.g., large files, slow connections, disconnections mid-stream).

Please add comprehensive unit and integration tests to cover:

1. Sending various types of P2PRequestBodyStream (e.g., string, Uint8Array, ArrayBufferView.
2. Sending an empty stream.
3. Sending a very large stream (mocking or actual).
4. Error handling during stream write.
5. Ensure retries correctly re-send the stream argument (as it's just a reference, but needs to be clear it's not consumed on first attempt if that's the intention, or if it needs to be recreated).
   • [WARNING][style] Consider adding JSDoc comments for the new requestBody parameter in dialAndStream and send methods to clearly explain its purpose and the types it accepts, improving API documentation for consumers.