refactor: merge VimMode into the api abstraction

[saidelike]

This is an attempt to refactor the code in order to abstract everything into the VimApi abstraction. This PR only deals with VimMode and merge it into VimApi.

Other parts could be merged later, but this is just the starting point if we agree to go this way. I would rather have this merged before going further.

[fidgetingbits]

I still need to look at this, but two questions:

1. Did you actually refactor anything from the code that was originally in talon-vim? If not, I won't bother diffing to see what you changed and mostly focus on testing, since I know the code worked anyway.

2. What did you do to test that I should replicate exactly? Just uninstall pynvim and make sure basic functionality still works? I just want to make sure that the baseline expectations you have for doing this still work on linux, but I already forget what they were.

[saidelike]

I still need to look at this, but two questions:

1. Did you actually refactor anything from the code that was originally in talon-vim? If not, I won't bother diffing to see what you changed and mostly focus on testing, since I know the code worked anyway.

This PR is a simple refactor of what there was in talon-vim. The idea is to cleanup the code in order to make it easier to maintain. It should not change its functionality. So testing any command that uses RPC is good indeed.

2. What did you do to test that I should replicate exactly? Just uninstall pynvim and make sure basic functionality still works? I just want to make sure that the baseline expectations you have for doing this still work on linux, but I already forget what they were.

I am not sure to follow why you want to uninstall pynvim. This PR still uses pynvim. It is just code refactoring to make it easier to maintain from now on.

[fidgetingbits]

I think if you add the inheritance and rebase to fix the merge conflicts this is fine. I took it for a spin and it seems to work fine.

I dunno why bought I thought this whole PR was something way more complicated, even after taking a quick glance last time, that was gonna cause a bunch of conflicts with talon-vim but is totally something different.

I'll file an issue, but just something to note is the fact that the class inheritance didn't exist and didn't cause any issues makes me think it's worth doing a big typing pass where everything is strongly typed, and then enforce it with mypy.

[fidgetingbits]

This should be a subclass of VimApiInternal ya?

[fidgetingbits]

This is probably causing a merge conflict as we removed auto=auto iirc