Fix MCP project resolution provenance

[clavery]

Summary

• make the compact resolution block authoritative and remove conflicting top-level project-directory provenance from config inspection and debugger session start results
• keep absolute local paths out of tool schema descriptions while documenting the server-directory-to-cwd fallback and pointing callers to config_inspect
• clarify that documentation workspace auto-detection is server-startup scoped
• add unit and production MCP end-to-end regression coverage

Validation

• pnpm --filter @salesforce/b2c-dx-mcp run pretest
• pnpm --filter @salesforce/b2c-dx-mcp run test:ci
• pnpm --filter @salesforce/b2c-dx-mcp run lint
• pnpm run test:agent
• pnpm run lint:agent
• pnpm run typecheck:agent
• pnpm run docs:build
• pnpm --filter @salesforce/b2c-dx-mcp... run build
• pnpm --filter @salesforce/b2c-dx-mcp run test:e2e

Repository-wide format checking still reports the pre-existing packages/b2c-vs-extension/src/cip-analytics/cip-styles.css formatting issue from main; all changed files pass formatting checks.

[github-actions]

📘 Docs preview

🧹 The preview for this PR has been removed (PR closed).