WKBCH-26: Launch vault via node instead of yarn start

Vault 7.89.0 ships an .npmrc referencing ${NODE_AUTH_TOKEN} for build-time
package authentication. Invoking yarn at container start makes yarn read
that file and abort with 'Failed to replace env in config: ${NODE_AUTH_TOKEN}'
because the variable is unset at runtime.

Match the production Vault and MetaData pattern by launching the node entry
point directly. This is what 'yarn start' resolves to (see Vault's package.json)
and avoids reading the .npmrc altogether.

Author: dvasilas

templates/global/docker-compose.yaml

@@ -120,7 +120,7 @@ services:
     image: ${VAULT_IMAGE}
     container_name: workbench-vault
     network_mode: host
-    command: sh -c "chmod 400 tests/utils/keyfile && yarn start"
+    command: sh -c "chmod 400 tests/utils/keyfile && node --max-http-header-size=32768 vaultd.js"
     environment:
       VAULT_DB_BACKEND: LEVELDB
     volumes: