Categorize new Neovim plugins and insert them into the correct markdown category files
Update each repo's plugin in the right markdown section, then create .reason.md summarizing why each category was chosen.
cat .new_plugins.txt..reason.md table, set the Category column to - and write the exclusion reason in the Reason column.
references/SECTION.md, consult the table of contents and locate the markdown file that contains that category.
3.3. Open that markdown file and insert the added plugin at the appropriate position. - If no suitable section exists, create one first and then add the plugin. - If there are subsections, review them and add the plugin to the whenever possible. - Add new plugins at the bottom of the section. - If there are related plugins, list them below the relevant plugin.filename / Section / Sub-section / ... (e.g., lsp.md / LSP / Diagnostics, editing.md / Editing / Indent / Auto-indent). Include as many levels as the actual heading hierarchy requires. If there is no sub-section, omit it (e.g., git-github.md / Git).Use this format for plugin entries:
- [author/plugin-name](https://github.com/author/plugin-name)   
Please make the necessary edits to improve categorization accuracy.