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
This forces vim to consider using omaps instead of incorrect normal ones
when executing a macro. Taking this approach because it does not seem
to cause any side-effects and still allows user customization of maps
under the existing lhs/rhs.
