fix(e2e): add missing .npmrc and fix transport assertion in node-express-mcp-v2

Without .npmrc, pnpm resolves @sentry/* from the public registry instead of
Verdaccio, so the published validateMcpServerInstance (v1-only) rejects the
v2 McpServer and no instrumentation is applied — causing the 30s timeout.

Also fix the mcp.transport assertion: NodeStreamableHTTPServerTransport
proxies onmessage to its inner WebStandardStreamableHTTPServerTransport,
so constructor.name in the wrapper is the inner class. Use the broader
/StreamableHTTPServerTransport/ regex (matching the v1 test pattern).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: betegon

dev-packages/e2e-tests/test-applications/node-express-mcp-v2/.npmrc

@@ -0,0 +1,2 @@
+@sentry:registry=http://127.0.0.1:4873
+@sentry-internal:registry=http://127.0.0.1:4873

dev-packages/e2e-tests/test-applications/node-express-mcp-v2/tests/mcp.test.ts

@@ -26,7 +26,7 @@ test('Should record transactions for MCP handlers using @modelcontextprotocol/sd
     expect(initializeTransaction.contexts?.trace?.data?.['mcp.method.name']).toEqual('initialize');
     expect(initializeTransaction.contexts?.trace?.data?.['mcp.client.name']).toEqual('test-client-v2');
     expect(initializeTransaction.contexts?.trace?.data?.['mcp.server.name']).toEqual('Echo-V2');
-    expect(initializeTransaction.contexts?.trace?.data?.['mcp.transport']).toMatch(/NodeStreamableHTTPServerTransport/);
+    expect(initializeTransaction.contexts?.trace?.data?.['mcp.transport']).toMatch(/StreamableHTTPServerTransport/);
   });
 
   await test.step('registerTool handler', async () => {