Explicitly return a stream-fatal error in cases where a change stream cannot be automatically resumed

At present, change streams may throw a variety of different error codes depending on the specific failure it encountered, such as InternalError, TooManyMatchingDocuments, or an unnamed code like 40576. Drivers do not recognise these as non-resumable exceptions, which can lead them to enter an infinite retry loop on a sharded cluster.