Fix parsing of docker STDOUT

[SkymanOne]

Summary

Closes #1455

• y/n | Does it introduce breaking changes?
• y/n | Is it dependent on the specific version of ink or pallet-contracts?

It was previously common to see the following error at the end of a verifiable build, even when the build was successful:

The previous implementation expected the BuildResult to be sent in a stream as a whole chunk of bytes. However, there can be cases when the data is sent in multiple chunks, which results in incorrect parsing.

We simply collect the byte chunks and then attempt to decode them together.

Checklist before requesting a review

• My code follows the style guidelines of this project
• I have added an entry to CHANGELOG.md
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• Any dependent changes have been merged and published in downstream modules

[smiasojed]

I think it would be great to have a CI test, which could catch issues like this.

[SkymanOne]

I think it would be great to have a CI test, which could catch issues like this.

The problem is that we need to have a nested docker environment. Idk if it's possible to run docker container inside another container.

[smiasojed]

I think it would be great to have a CI test, which could catch issues like this.

The problem is that we need to have a nested docker environment. Idk if it's possible to run docker container inside another container.

I do not see any docker image used for CI, it seems that we are building this directly on the runner

[SkymanOne]

I think it would be great to have a CI test, which could catch issues like this.

The problem is that we need to have a nested docker environment. Idk if it's possible to run docker container inside another container.

I do not see any docker image used for CI, it seems that we are building this directly on the runner

Sure, I'll do it in the follow up PR then

[cmichi]

Sure, I'll do it in the follow up PR then

@SkymanOne Please create a GitHub issue for it and assign it to yourself.