Fixing random CI failures due to message skips

[aryanjassal]

Description

This PR focuses on resolving #70, which is a critical bug that happens in the CI because the second message is skipped.

Issues Fixed

• Fixes Transferring data through the RPC stream skips the second message #70 (FIX ENG-465)

Tasks

• 1. Fix the error
• 2. Run all tests to ensure the error isn't present
• 3. Change the method from cancelling and attaching streams to instead be more dynamic like returning a promise for the header.

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[linear]

ENG-465 Transferring data through the RPC stream skips the second message

[aryanjassal]

I removed a couple tests from the files as they were redundant and literally duplicating code. Some others, I feel like they might be redundant. I will be going through the changes in-depth tomorrow and make a brief list discussing the reasoning behind the test removals.

Also, the formatting, while correct, was too verbose. I re-formatted the code, which is the main culprit in adding a lot of lines changed in this commit.

However, in conclusion, basically everything is working at this point, and the weird stream plumbing has been replaced with a more elegant solution as a special transform stream which returns the JSON header message after parsing and returns the following as raw bytes without applying any processing on it.

The CI for this change is passing, both locally and on github. The only way to see if the change is actually made and is consistent is to merge it to staging and see whether the CI breaks or not.

Also, @brynblack still needs to set up auto deployment for this repo. Maybe after I have merged this PR and (hopefully) fixed the CI, you can merge a quick fix for that.

[CMCDragonkai]

This is a blocker, please address this asap @brynblack.

[aryanjassal]

Just need some general inputs on some things.

[CMCDragonkai]

Did this change any expected behaviour at the UI level?

[aryanjassal]

Did this change any expected behaviour at the UI level?

No, there was no external change to using the streams in any way. This PR just changed internal code related to retrieval of the header message to use a more elegant system instead of replumbing streams.