Broaden types in StreamableFile constructor

Editor assessment

Broadening the types accepted by the StreamableFile constructor names the API and the direction of the change, but broadened is never specified: which new input types — buffers, streams, typed arrays — are now valid, and what motivated the widening, is left to the diff. No body supplies the motivation or the new contract, so consumers cannot learn the accepted shapes from history. feat(common) types and scopes the change correctly. No footers appear. Hygiene is clean — imperative mood, no trailing period — but the message stays abstract where specifics were available.