Stop using `Symbol.dispose`

[rijenkii]

Using Symbol.dispose right now is a bad idea. It is only supported starting with chrome 134, and Explicit Resource Management proposal is only at stage 3 of 4.

Fix released in 3.0.1 does not work, judging by comments on #260 and my own experience.

[rijenkii]

Fix submitted, waiting for review.

[nuintun]

Symbol.dispose is available and correctly transpiled by TypeScript, but it's polyfill being removed during bundler tree-shaking due to misconfigured sideEffects settings.

See: #270