fix(benchmark): set proper audience to introspect token (#11586)

# Which Problems Are Solved

Benchmark appears to run correctly, however the token used isn't valid.
The backend (Zitadel 4.11-pre) prints a constant stream of info logs
that the token isn't valid for the client.

# How the Problems Are Solved

Pass the generated project IDs as a scope for a new login.

# Additional Changes

- ensure keys for introspection and add session recipes.

# Additional Context

- Closes #11585

---------

Co-authored-by: Silvan <[email protected]>

benchmark/package-lock.json

@@ -1,12 +1,11 @@
 {
-    "name": "typescript",
+    "name": "@zitadel/benchmark",
     "version": "1.0.0",
     "lockfileVersion": 3,
     "requires": true,
     "packages": {
         "": {
-            "name": "typescript",
-            "version": "1.0.0",
+            "name": "@zitadel/benchmark",
             "license": "Apache-2.0",
             "devDependencies": {
                 "@babel/core": "7.23.7",