update tasks.json (#2313)

bring the tasks.json up to date 
- The VM is the default path now so no need for it
- The tokens option is no longer available

.vscode/tasks.json

@@ -22,53 +22,14 @@
       },
       "problemMatcher": []
     },
-    {
-      "type": "process",
-      "label": "Cargo Run (VM)",
-      "command": "cargo",
-      "args": ["run", "--", "-t", "../tests/js/test.js"],
-      "group": {
-        "kind": "build",
-        "isDefault": true
-      },
-      "presentation": {
-        "clear": true
-      },
-      "options": {
-        "cwd": "${workspaceFolder}/boa_cli",
-        "env": {
-          "RUST_BACKTRACE": "1"
-        }
-      },
-      "problemMatcher": []
-    },
     {
       "type": "process",
       "label": "Cargo Run (Profiler)",
       "command": "cargo",
-      "args": ["run", "--features", "Boa/profiler", "../tests/js/test.js"],
-      "group": "build",
-      "options": {
-        "env": {
-          "RUST_BACKTRACE": "full"
-        },
-        "cwd": "${workspaceFolder}/boa_cli"
-      },
-      "presentation": {
-        "clear": true
-      },
-      "problemMatcher": []
-    },
-    {
-      "type": "process",
-      "label": "Cargo Run (Profiler & VM)",
-      "command": "cargo",
       "args": [
         "run",
         "--features",
-        "Boa/profiler",
-        "--features",
-        "vm",
+        "boa_engine/profiler",
         "../tests/js/test.js"
       ],
       "group": "build",
@@ -85,9 +46,9 @@
     },
     {
       "type": "process",
-      "label": "Get Tokens",
+      "label": "Run with VM trace",
       "command": "cargo",
-      "args": ["run", "--bin", "boa", "--", "-t=Debug", "./tests/js/test.js"],
+      "args": ["run", "--bin", "boa", "--", "-t", "./tests/js/test.js"],
       "group": "build",
       "presentation": {
         "clear": true

docs/profiling.md

@@ -19,7 +19,7 @@ when the feature flag is not enabled, you have an empty dummy implementation tha
 
 You can run boa using the "profiler" feature flag to enable profiling. Seeing as you'll most likely be using boa_cli you can pass this through, like so:
 
-`cargo run --release --features Boa/profiler ../tests/js/test.js`
+`cargo run --release --features boa_engine/profiler ../tests/js/test.js`
 
 Once finished you should see some trace files left in the directory (boa_cli in this case).  
 In the same directory as the `.events, string_data, string_index` files run `crox my_trace` or whatever the name of the files are. This will generate a chrome_profiler.json file, you can load this into Chrome Dev tools.