fix(NODE-4475): make interrupted message more specific

[durran]

Description

Fixes change stream retryability on 4.4 servers and lower when performing a failover.

What is changing?

This is the "quick and dirty" fix that just avoids pushing a null to the readable cursor stream before calling destroy on the stream when the error contains the message "interrupted at shutdown".

Existing spec tests cover the more specific error - see: https://github.com/mongodb/node-mongodb-native/blob/main/test/spec/retryable-writes/legacy/insertOne-serverErrors.yml#L468

Note: see #3438 for what a start of a refactor away from checking for this error message and creating separate streams for the change stream cursor and the others would look like. However it seems the "operation was interrupted" message affects change streams as well so I'll leave it as draft for now.

Is there new documentation needed for these changes?

None

What is the motivation for this change?

NODE-4475

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>
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[baileympearson]

From tech chat - let's try to add tests that

• confirm a change stream resumes if it encounters a resumable error with interrupted in the error message
• confirm that a change stream does not resume if it encounters an error with operation was interrupted as the message

Also - @durran want to file a follow up ticket to investigate removing the two special cases here?

[durran]

From tech chat - let's try to add tests that

* confirm a change stream resumes if it encounters a resumable error with `interrupted` in the error message

* confirm that a change stream does not resume if it encounters an error with `operation was interrupted` as the message

Also - @durran want to file a follow up ticket to investigate removing the two special cases here?

https://jira.mongodb.org/browse/NODE-4717 is created.