feat: Bundle client code in server package

Since the ESM output of the client package cannot currently
run in Node.js in ESM mode, we may need to run end-to-end
tests in Node.js that interact with both the client and server code.

It makes sense to remove server code from the client bundle,
but not so much the other way around where size is less constrained.

package.json

@@ -25,7 +25,7 @@
     "clean:server": "rm -rf packages/server/*",
     "clean:client": "rm -rf packages/client/*",
     "build": "run-s build:*",
-    "build:server": "wasm-pack build --out-dir ../../packages/server --scope 47ng --out-name opaque-server --release --target nodejs submodules/opaque-wasm --no-default-features --features server",
+    "build:server": "wasm-pack build --out-dir ../../packages/server --scope 47ng --out-name opaque-server --release --target nodejs submodules/opaque-wasm",
     "build:client": "wasm-pack build --out-dir ../../packages/client --scope 47ng --out-name opaque-client --release --target web    submodules/opaque-wasm --no-default-features --features client",
     "patch": "./scripts/patch-packages.sh"
   },