docs migration - Configuring Neovim for Swift Development

Source: documentation/articles/zero-to-swift-nvim.md
Proposed disposition: Migrate
Proposed destination: ecosystem-tools/Sources/EcosystemTools.docc/zero-to-swift-nvim.md
Reviewer: @swiftlang/ecosystem-steering-group

Checklist

• Create a GitHub issue to track this migration
• Determine disposition (suggested: Migrate) and confirm destination
• Review source for accuracy against current Neovim plugin ecosystem (lazy.nvim, nvim-cmp, LuaSnip) and SourceKit-LSP
• Translate Jekyll markdown to DocC markdown format
  • Remove YAML front matter
  • Convert any Jekyll callouts to DocC-style callouts
  • Verify plugin configuration snippets compile and function correctly
  • Update any version-pinned references in plugin configurations
• Add article to EcosystemTools.docc/Documentation.md under an "Editor Configuration" topic group
• Run swift package generate-documentation --analyze --warnings-as-errors in ecosystem-tools/
• Preview locally with swift package --disable-sandbox preview-documentation in ecosystem-tools/
• Submit PR to this repository for ecosystem steering group review
• After merge and publication: add redirect_to: in the swift.org source file's front matter
• Submit redirect PR to swift-org-website

Start with documentation/articles/zero-to-swift-nvim.md and compare it with the proposed destination ecosystem-tools/Sources/EcosystemTools.docc/zero-to-swift-nvim.md. Review the Neovim plugin and SourceKit-LSP references, convert the document for DocC, add it to Documentation.md, and run the two listed documentation commands in ecosystem-tools/. Done means the article is validated, previewable, published, and the source redirect PR is prepared.