The `goto` keyword is introduced in a newer version of lua, running this
plugin with an older version of lua will produce an error:
```
Error detected while processing function matchup#loader#bufwinenter[4]..matchup#loader#init_buffer[5]..matchup#ts_engine#is_enabled[4]..<SNR>126_forward:
line 1:
E5108: Error executing lua vim.lua:63: ...local/share/nvim/plugins/vim-matchup/lua/treesitter-matchup/internal.lua:195: '=' expected near 'continue'
stack traceback:
[C]: in function 'error'
vim.lua:63: in function <vim.lua:57>
[C]: in function 'require'
[string "luaeval()"]:1: in main chunk
Error detected while processing function matchup#loader#bufwinenter[4]..matchup#loader#init_buffer[15]..matchup#ts_engine#is_hl_enabled[4]..<SNR>126_forward:
line 1:
E5108: Error executing lua vim.lua:63: ...local/share/nvim/plugins/vim-matchup/lua/treesitter-matchup/internal.lua:195: '=' expected near 'continue'
stack traceback:
[C]: in function 'error'
vim.lua:63: in function <vim.lua:57>
[C]: in function 'require'
[string "luaeval()"]:1: in main chunk
Error detected while processing function matchup#loader#init_buffer[5]..matchup#ts_engine#is_enabled[4]..<SNR>126_forward:
line 1:
E5108: Error executing lua vim.lua:63: ...local/share/nvim/plugins/vim-matchup/lua/treesitter-matchup/internal.lua:195: '=' expected near 'continue'
stack traceback:
[C]: in function 'error'
vim.lua:63: in function <vim.lua:57>
[C]: in function 'require'
[string "luaeval()"]:1: in main chunk
```
This commit removes the goto keyword to avoid such error. Has been
tested on debian testing.
Related: https://github.com/AaronJackson/vrn/issues/157
Previously, placing the cursor on line 1 would highlight every elif and
else in the whole block of code. % would jump to line 4, then % from
there would cycle between lines 2, 4 and 6.
1 if noice:
2 if yeah:
3 pass
4 elif no:
5 pass
6 else:
7 pass
8 elif blah:
9 pass
10 else:
11 pass
With the change, which I think the code had contemplated given there was
already an unused `M.containing_scope(node, bufnr, info.key)` call, % will
only move between ifs and elses that are in the same `@scope.if_`, and
not to any inner scopes. Hence the example will have two mutually
exclusive %-cycles: [1, 8, 10] and [2, 4, 6].
