test(mcp): authenticate equivalence smokes with the expert-mcp platform token

Mint the nameless user:expert-mcp platform token via createExpertMcpToken
instead of a named personal access token, so the search tool smoke tests
go through the same IMPLICIT_TOKEN_SCOPES allow-list check the Expert
uses in production.

Author: andypalmi

test/unit/forge/ee/lib/mcp/tools/search_spec.js

@@ -1,6 +1,6 @@
 const should = require('should') // eslint-disable-line no-unused-vars
 
-const { expectToolMatchesRoute } = require('../../../../../../lib/mcpToolEquivalence')
+const { expectToolMatchesRoute, createExpertMcpToken } = require('../../../../../../lib/mcpToolEquivalence')
 
 const FF_UTIL = require('flowforge-test-utils')
 const tools = FF_UTIL.require('forge/ee/lib/mcp/tools/search')
@@ -66,11 +66,11 @@ describe('MCP Search Tools', function () {
         const setup = require('../../../setup')
 
         let app
-        let pat
+        let token
 
         before(async function () {
             app = await setup({ ai: { enabled: true }, expert: { enabled: true } })
-            pat = await app.db.controllers.AccessToken.createPersonalAccessToken(app.user, '', null, 'smoke-pat')
+            token = await createExpertMcpToken(app)
         })
 
         after(async function () {
@@ -81,7 +81,7 @@ describe('MCP Search Tools', function () {
             ...options,
             headers: {
                 ...(options.headers || {}),
-                authorization: `Bearer ${pat.token}`
+                authorization: `Bearer ${token}`
             }
         })