Fix missing memory tool provisioning for GPT-5.4

[dpearson2699]

Summary

Fixes the missing vscode/memory tool provisioning for GPT-5.4 by keeping memory as a core tool instead of grouping it under VS Code interaction tools.

This change:

• reclassifies ToolName.Memory as a core tool so it remains directly available
• adds a regression test covering the built-in tool grouping behavior

Fixes #309245

Validation

• npm run compile-extensions-build
• npm --prefix extensions/copilot run test:unit -- src/extension/tools/test/node/virtualTools/builtInToolGroupHandler.spec.ts
• node --experimental-strip-types build/hygiene.ts extensions/copilot/src/extension/tools/common/toolNames.ts extensions/copilot/src/extension/tools/test/node/virtualTools/builtInToolGroupHandler.spec.ts

[Copilot]

Pull request overview

Fixes deterministic absence of the vscode/memory tool for GPT-5.4 by ensuring ToolName.Memory is treated as a Core tool (excluded from built-in tool grouping), and adds a regression test to lock in the intended grouping behavior.

Changes:

• Reclassifies ToolName.Memory from ToolCategory.VSCodeInteraction to ToolCategory.Core so it won’t be grouped away.
• Adds a unit test verifying that VS Code interaction tools are grouped while memory remains individually available.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
extensions/copilot/src/extension/tools/common/toolNames.ts	Moves ToolName.Memory into the Core category to prevent it from being grouped.
extensions/copilot/src/extension/tools/test/node/virtualTools/builtInToolGroupHandler.spec.ts	Adds regression coverage ensuring memory stays ungrouped while VS Code interaction tools are grouped.

[dpearson2699]

@microsoft-github-policy-service agree