[Tracking] Error rework to use concrete types

[crowlKats]

Exts:

• broadcast_channel refactor(ext/broadcastchannel): use concrete error type #26105
• cache refactor(ext/cache): use concrete error type #26109
• canvas refactor(ext/canvas): use concrete error type #26111
• cron refactor(ext/cron): use concrete error type #26135
• crypto refactor(ext/crypto): use concrete error types #26167
• fetch refactor(ext/fetch): use concrete error types #26220
• ffi refactor(ext/ffi): use concrete error types #26170
• fs refactor(ext/fs): use concrete error types #26317
• http refactor(ext/http): use concrete error types #26377
• io refactor(ext/io): use concrete error types #26187
• kv refactor(ext/kv): use concrete error type #26239
• napi refactor(ext/napi): use concrete error types #26186
• net refactor(ext/net): use concrete error type #26227
• node refactor(ext/node): use concrete error types #26419
• tls refactor(ext/tls): use concrete error types #26174
• url refactor(ext/url): use concrete error types #26172
• web refactor(ext/web): use concrete error types #26185
• webgpu refactor(ext/webgpu): use concrete error type #26198
• websocket refactor(ext/websocket): use concrete error type #26226
• webstorage refactor(ext/webstorage): use concrete error types #26173

Others (to do after the exts, in order):

• Runtime Ops refactor(runtime/ops): use concrete error types #26409
• Permissions refactor(runtime/permissions): use concrete error types #26464
• Runtime refactor: update deno_core for error rework #25211
• CLI
• deno_core refactor: rework error handling deno_core#878