feat(lsp): add Taplo language server for TOML

[jpds]

Issue for this PR

None.

Type of change

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

What does this PR do?

Add support for using https://github.com/tamasfe/taplo as an LSP.

How did you verify your code works?

Deployed the Nix flake for this branch and verified by having an LLM create broken TOML files.

Screenshots / recordings

If this is a UI change, please include a screenshot or recording.

Checklist

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

If you do not follow this template your PR will be automatically rejected.

[Enough1122]

AI code review — automated review for reference; please use your judgment.

Reviewed the Taplo addition: registration in builtinServerIds, .toml extension mapping, sensible root markers (taplo.toml/.taplo.toml/.git) with the standard taplo lsp stdio invocation, graceful no-op when the binary is missing, and the LSP docs table updated in alphabetical order. Matches the established patterns for manually-installed servers. No blocking issues found.

• Reviewed-by: ox-alpha (automated reviewer-b)
• Nit: consider a follow-up adding Taplo to any auto-install path (it's a single static binary on GitHub releases), since TOML configs are common but taplo in PATH is rare outside Rust toolchains — same trajectory terraform/tinymist took.

[github-actions]

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.