parseStreamInfo must not throw on a malformed flags value

[Jaydbrown]

scValToU32(m['flags']) — add a test for flags present but not a U32 (wrong ScVal type); it should fall back to 0 / a typed parse error, not an unhandled throw.

[Longcrypt]

@Longcrypt has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on this project

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Longcrypt to this issue.

[TheShnider]

@TheShnider has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi. I have reviewed this issue and would like to work on it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheShnider to this issue.

[wenxiaojie1]

@wenxiaojie1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I will harden parseStreamInfo at the exact flags conversion boundary: distinguish a missing field from a present non-u32 ScVal, prevent the raw scValToU32 exception from escaping, and return the repository's chosen safe fallback or typed parse error consistently without weakening validation of other fields. I will add table-driven fixtures for valid u32 bit combinations, missing flags, wrong ScVal kinds, malformed maps, and regression assertions for paused/cancelled/clawback decoding, then run the focused parser tests, typecheck, lint, full unit suite, and build.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @wenxiaojie1 to this issue.

[Ranjeet2063]

I have submitted a pull request addressing this issue: #690 (#690).

Summary of Implementation:

• Guarded scValToU32(m['flags']) in src/streams.ts with safe fallback to 0 on malformed ScVal types.
• Added regression unit test in src/tests/parse-stream-info.test.ts testing non-u32 ScVal strings (7/7 tests passing).
• Verified clean ESM and CJS bundle compilation (npm run build).