rename isSDAMUnrecoverableError to match spec's name

Author: baileympearson

src/error.ts

@@ -1528,13 +1528,7 @@ export function isNodeShuttingDownError(err: MongoError): boolean {
  *
  * @see https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/server-discovery-and-monitoring.md#not-writable-primary-and-node-is-recovering
  */
-export function isSDAMUnrecoverableError(error: MongoError): boolean {
-  // NOTE: null check is here for a strictly pre-CMAP world, a timeout or
-  //       close event are considered unrecoverable
-  if (error instanceof MongoParseError || error == null) {
-    return true;
-  }
-
+export function isStateChangeError(error: MongoError): boolean {
   return isRecoveringError(error) || isNotWritablePrimaryError(error);
 }
 

src/sdam/server.ts

@@ -22,12 +22,13 @@ import {
 import {
   type AnyError,
   isNodeShuttingDownError,
-  isSDAMUnrecoverableError,
+  isStateChangeError,
   MONGODB_ERROR_CODES,
   MongoError,
   MongoErrorLabel,
   MongoNetworkError,
   MongoNetworkTimeoutError,
+  MongoParseError,
   MongoRuntimeError,
   MongoServerClosedError,
   type MongoServerError,
@@ -412,7 +413,14 @@ export class Server extends TypedEventEmitter<ServerEvents> {
         this.pool.clear({ serviceId: connection.serviceId });
       }
     } else {
-      if (isSDAMUnrecoverableError(error)) {
+      // TODO: considering parse errors as SDAM unrecoverable errors seem
+      // questionable.  What if the parse error only comes from an application connection,
+      // indicating some bytes were lost in transmission?  It seems overkill to completely
+      // kill the server.
+      // Parse errors from monitoring connections are already handled because the
+      // error would be wrapped in a ServerHeartbeatFailedEvent, which would mark the
+      // server unknown and clear the pool.  Can we remove this?
+      if (isStateChangeError(error) || error instanceof MongoParseError) {
         if (shouldHandleStateChangeError(this, error)) {
           const shouldClearPool = isNodeShuttingDownError(error);
           if (this.loadBalanced && connection && shouldClearPool) {