build: Patch socket.io packages for node16 moduleResolution (#18170)

This PR patches socket.io-client and engine.io-client, applying the
changes from socketio/socket.io-client#1595 and
socketio/engine.io-client#711, respectively.

I think this is a safe change because we are using only types from the
package, and the .d.ts/exported API still refers to the real
socket.io-client package, so consumers should see no difference - they
might still hit the same bug we're hitting, but only when using node16
moduleResolution.


[AB#6140](https://dev.azure.com/fluidframework/235294da-091d-4c29-84fc-cdfc3d90890b/_workitems/edit/6140)

package.json

@@ -365,6 +365,10 @@
 				"@types/node",
 				"fluid-framework"
 			]
+		},
+		"patchedDependencies": {
+			"[email protected]": "patches/[email protected]",
+			"[email protected]": "patches/[email protected]"
 		}
 	}
 }

patches/README.md

@@ -0,0 +1,26 @@
+# Dependency patches
+
+The files in this folder are patches for packages we depend on within the repo. The patches are created using
+[pnpm patch](https://pnpm.io/cli/patch), and pnpm applies the patches automatically when running install.
+
+## Patch details
+
+Each patch is described here, along with any relevant links to issues or PRs and any additional relevant details.
+
+### engine.io-client
+
+This patch updates the `exports` field in package.json to be correct for TypeScript projects using
+`moduleResolution: node16`.
+
+It applies the changes covered in this PR: https://github.com/socketio/engine.io-client/pull/711
+
+As soon as a version of the package is released with the changes in that PR, this patch can be removed.
+
+### socket.io-client
+
+This patch updates the `exports` field in package.json to be correct for TypeScript projects using
+`moduleResolution: node16`.
+
+It applies the changes covered in this PR: https://github.com/socketio/socket.io-client/pull/1595
+
+As soon as a version of the package is released with the changes in that PR, this patch can be removed.