feat(ext/net): relevant errors for resolveDns

[satyarohith]

This PR maps resolveDns errors to Deno errors where applicable.

DNS protocol errors are still returned as generic errors. I'm
not sure if we should create a new DNSError class for them.

Closes #9197

[kt3k]

Is it possible to write test cases which exercise some of these code paths?

[lucacasonato]

DNS protocol errors are still returned as generic errors. I'm
not sure if we should create a new DNSError class for them.

I think a Deno.errors.Dns might be useful indeed.

[satyarohith]

Is it possible to write test cases which exercise some of these code paths?

Updated an existing test for NotFound. It might be complicated to exercise NotConnected and TimedOut

[satyarohith]

DNS protocol errors are still returned as generic errors. I'm
not sure if we should create a new DNSError class for them.

I think a Deno.errors.Dns might be useful indeed.

I'm open but also a little hesitant as it feels like the protocol errors are very uncommon.

[kt3k]

LGTM as this is definitely better than the current state, but I think we can do more work about this

cc @magurotuna Do you have any opinion about this?

[bartlomieju]

LGTM

[satyarohith]

@magurotuna, I'm merging this PR for the time being. Would you mind letting me know if you have any thoughts on this change? I'll make a PR if you suggest any changes.