db.response.status_code type is string per the OTel convention https://opentelemetry.io/docs/specs/semconv/registry/attributes/db/

Author: nhachicha

source/open-telemetry/tests/operation/find_retries.json

@@ -95,7 +95,7 @@
                     "db.mongodb.cursor_id": {
                       "$$exists": false
                     },
-                    "db.response.status_code": 89,
+                    "db.response.status_code": "89",
                     "exception.message": {
                       "$$type": "string"
                     },

source/open-telemetry/tests/operation/find_retries.yml

@@ -57,7 +57,7 @@ tests:
                   db.command.name: find
                   network.transport: tcp
                   db.mongodb.cursor_id: { $$exists: false }
-                  db.response.status_code: 89
+                  db.response.status_code: '89'
                   exception.message: { $$type: string }
                   exception.type: { $$type: string }
                   exception.stacktrace: { $$type: string }

source/open-telemetry/tests/operation/retries.json

@@ -101,7 +101,7 @@
                     "db.mongodb.cursor_id": {
                       "$$exists": false
                     },
-                    "db.response.status_code": 89,
+                    "db.response.status_code": "89",
                     "exception.message": {
                       "$$exists": true
                     },

source/open-telemetry/tests/operation/retries.yml

@@ -61,7 +61,7 @@ tests:
                   db.command.name: find
                   network.transport: tcp
                   db.mongodb.cursor_id: { $$exists: false }
-                  db.response.status_code: 89
+                  db.response.status_code: '89'
                   exception.message: { $$exists: true }
                   exception.type: { $$exists: true }
                   exception.stacktrace: { $$exists: true }