Tests for typescriptreact are failing on main

[PriceHiller]

Seems an update upstream in nvim-treesitter has broken our tests, need to update our typescriptreact configuration to work with the upstream changes.

[r-ricci]

@PriceHiller I don't know how to run the test suite, but I can see that this plugin does not work on typescriptreact files.

The issue seems to be that tree-sitter-typescript doesn't know about "typescriptreact", but calls it "tsx" instead (https://github.com/tree-sitter/tree-sitter-typescript/blob/75b3874edb2dc714fb1fd77a32013d0f8699989f/README.md?plain=1#L12,L17).

We can use vim.treesitter.language.register() to make vim.treesitter.get_parser() return the correct parser for the filetype.

This works for me:

diff --git a/lua/nvim-ts-autotag/config/plugin.lua b/lua/nvim-ts-autotag/config/plugin.lua
index 418bc7d..fb923f5 100644
--- a/lua/nvim-ts-autotag/config/plugin.lua
+++ b/lua/nvim-ts-autotag/config/plugin.lua
@@ -228,6 +228,11 @@ function Setup.setup(opts)
             end,
         })
     end
+
+    --vim.treesitter.language.register("javascript", "javascript") -- implicit
+    vim.treesitter.language.register("javascript", "javascriptreact")
+    vim.treesitter.language.register("tsx", "typescript")
+    vim.treesitter.language.register("tsx", "typescriptreact")
 end
 
 --- Get the defined options for the given filetype or in general

I'm not making a PR because I'm not sure what's the most appropriate place to put this code and whether to use "tsx" for all four filetypes.

[r-ricci]

This feels like something which should be fixed by nvim itself, rather than having every single plugin calling vim.treesitter.language.register().
Until this gets fixed, I think we could suggest users to add these calls to their init.lua.