Safari fix: refactor Stream Parses to use while(true) instead of for await

[ninaceban]

Description

In previous version we were using for await(chunks in stream) which was causing issues in Safari. Safari does have support for for await syntax. The problem is that Safari's ReadableStream class does not implement Symbol.asyncIterator on its prototype.

The solution is to refactor the code to use stream.getReader() and while(true), catch, finally block.

Related Issue

Motivation and Context

Screenshots (if appropriate):

Checklist:

• I have signed the Adobe Open Source CLA or I'm an Adobe employee.
• I have made any necessary test changes and all tests pass.
• I have run the Sandbox successfully.
• I have added a Changeset (pnpm changeset) or it is not necessary because this PR is not consumer-facing.

[changeset-bot]

🦋 Changeset detected

Latest commit: 5e6735c

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[carterworks]

Please run pnpm changeset, select @adobe/alloy, and write what you want to go on the public changelog file

[dompuiu]

This PR seems ok. Please do what Carter asked.

As I already told you, there are some potential issues that could be fixed. I sent you the list on Slack.

[jonsnyder]

Looks good. Can you remove the hard-coded 10 seconds in this error message:

alloy/packages/core/src/components/BrandConcierge/createTimeoutWrapper.js

Line 34 in 0abf50a

message: "Stream timeout: No data received within 10 seconds",

[ninaceban]

Looks good. Can you remove the hard-coded 10 seconds in this error message:

alloy/packages/core/src/components/BrandConcierge/createTimeoutWrapper.js

Line 34 in 0abf50a

message: "Stream timeout: No data received within 10 seconds",

sure

Nina finished what he was asking for.