fix(opencode): fixed js lsp servers detection in monorepos

[tumenbaev]

Issue for this PR

Closes #7690

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

In monorepo setups, LSP servers for JavaScript/TypeScript languages (TypeScript, ESLint, and Astro) were failing to start because the module resolution for tsserver and eslint was using Instance.directory (the monorepo root) instead of the detected package root. This caused issues when TypeScript or ESLint were installed locally in individual packages rather than at the monorepo root. This is how biome is configured already and it works correctly.

The fix updates the Module.resolve calls in the spawn functions for TypeScript, ESLint, and Astro LSP servers to use the root parameter (the package-specific directory) instead of Instance.directory.

This ensures LSP servers can properly detect and use locally installed dependencies in monorepo environments.

How did you verify your code works?

I tested the changes in a monorepo setup with multiple JavaScript/TypeScript packages, verifying that LSP servers now start correctly and resolve dependencies from the correct package directories.

Screenshots / recordings

-

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Potential Duplicate Found:

• PR fix: eslint & tsserver lsp root detection #7691: "fix: eslint & tsserver lsp root detection"
  • fix: eslint & tsserver lsp root detection #7691

Why it's related: Both PRs address the same issue (#7690) about fixing LSP server root detection for ESLint and TypeScript in monorepo setups. PR #7691 appears to be the original fix for the exact same problem - fixing ESLint and tsserver LSP root detection to use the package-specific directory instead of the monorepo root.