refactor(test-tooling): fix types of streams: use NodeJS.ReadableStream

[petermetz]

1. The container management library that we use in the test infrastructure
   (called dockerode) is expecting streams that are defined in the global
   namespace of the @types/node library, e.g. the standard library of NodeJS
   itself.
2. Previously we were using the "streams" package to provide type information
   to the streams that we were passing around to dockerode and it was working
   fine, but after some changes that seem unrelated this has broken the
   compilation process.
3. The mentioned changes are not yet on the main branch, but we expect
   them to be there soon and so this change is laying the groundwork for that
   by pre-emptively fixing the broken build's root cause which is that the
   test-tooling package does not declare it's typings related dependencies
   correctly: It implicitly uses the NodeJS standard library's types but
   so far had not declared them on the package level.
4. This change is therefore to rectify the issue of the @types/node
   dependency missing from the test-tooling package and also the refactoring
   of some of the test ledger classes which were relying on the streams
   builtin package instead of correctly using the NodeJS.ReadableStream global.
5. Earlier the reasoning for this was that we try to avoid pulling in
   types from the global scope because we try to avoid any sort of dependency
   on the global scope in general. Once we have proof though that this is
   causing issues with the build, then we must give up the principle for
   practical reasons (and only in the minimum viable scope, e.g. this does
   not change the fact that everywhere else in the codebase we should still
   do our best to avoid using the global scoped classes, types, functions,
   etc..).

Thank you to @AndreAugusto11 and @RafaelAPB for pointing out this issue
through the pull request of his that is currently being worked on at the
time of this writing:
RafaelAPB#72

Related to but does not address #2811

Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[RafaelAPB]

One comment: 🥵. In a more serious tone, great work @petermetz and @AndreAugusto11

[jagpreetsinghsasan]

LGTM