fix: bump tlsn-wasm to alpha.7.1 and move to dependency (#71)

Author: 0xtsukino

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "tlsn-js",
-  "version": "0.1.0-alpha.7",
+  "version": "0.1.0-alpha.7.1",
   "description": "",
   "repository": "https://github.com/tlsnotary/tlsn-js",
   "main": "build/lib.js",
@@ -55,7 +55,6 @@
     "serve": "14.2.1",
     "serve-handler": "^6.1.5",
     "stream-browserify": "^3.0.0",
-    "tlsn-wasm": "0.1.0-alpha.7.1",
     "ts-loader": "^6.2.1",
     "ts-mocha": "^10.0.0",
     "ts-node": "^10.9.2",
@@ -70,5 +69,8 @@
   "license": "ISC",
   "engines": {
     "node": ">= 16.20.2"
+  },
+  "dependencies": {
+    "tlsn-wasm": "^0.1.0-alpha.7.2"
   }
-}
+}

package.json

@@ -31,7 +31,7 @@ For this demo, we also need to run a local notary server.
 
 1. Clone the TLSNotary repository:
    ```shell
-   git clone https://github.com/tlsnotary/tlsn.git --branch "v0.1.0-alpha.6"
+   git clone https://github.com/tlsnotary/tlsn.git --branch "v0.1.0-alpha.7"
    ```
 2. Edit the notary server config file (`notary/server/config/config.yaml`) to turn off TLS so that the browser extension can connect to the local notary server without requiring extra steps to accept self-signed certificates in the browser.
    ```yaml