fix(NODE-6864): socket errors are not always converted to MongoNetworkErrors

[nbbeeken]

Description

What is changing?

• Ensure socket errors are converted
• Do not squash error in finally block

Is there new documentation needed for these changes?

No

What is the motivation for this change?

Networking errors are handled specially for retry/resume logic, if we fail to wrap them in our Network error type we won't retry them.

Release Highlight

Socket errors are always treated as network errors

Network errors perform an important role in the driver, impacting topology monitoring processes and retryablity. A bug in the driver's socket implementation meant that in scenarios where server disconnects occurred while no operation was in progress on the socket resulted in errors that were not considered network errors.

Socket errors are now unconditionally treated as network errors.

Double check the following

• Ran npm run check:lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket