Implement ReadableStream.from - #32533

Node throws these iterator-protocol violations as `TypeError`s with `code: 'ERR_INVALID_STATE'` (e.g. `ReadableStream.from({[Symbol.asyncIterator](){return 5}})` → `.code === 'ERR_INVALID_STATE'`), but here they're plain `new TypeError(...)` with no `.code`. `$ERR_INVALID_STATE_TypeError` is already used elsewhere in this file (e.g. for "ReadableStream is locked"); swapping to it here — and at the `iterator.next()` non-object check (line 144) and the `iterator.return()` non-object check (lines 1

The runtime now exposes `ReadableStream.from`, but the bun-types fallback declaration (`packages/bun-types/globals.d.ts:73-80`) wasn't updated — the no-DOM `UseLibDomIfAvailable` constructor type still has only `prototype` and two `new` overloads. Server-only Bun projects without `"DOM"` in their tsconfig `lib` will get a TS error on `ReadableStream.from(...)` even though it works at runtime; adding `from<R>(asyncIterable: AsyncIterable<R> | Iterable<R | PromiseLike<R>>): ReadableStream<R>;` to 

`String(iterable)` invokes ToPrimitive, which throws for null-prototype objects (and any object with a throwing `toString`/`Symbol.toPrimitive`), so `ReadableStream.from(Object.create(null))` surfaces a bare "Cannot convert object to primitive value" TypeError with no `.code` instead of `ERR_ARG_NOT_ITERABLE`. Node uses inspect-style formatting here and returns `code: 'ERR_ARG_NOT_ITERABLE'` with message `[Object: null prototype] {} must be iterable`. Wrapping `String(iterable)` in a try/catch w