feat(editing-support): add mini-operators plugin

[manuuurino]

📑 Description

Making this a draft PR, because i am unsure which binding would match it neatly. I left there also an note on the source code.

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Proper usage of opts table rather than setting things up with the config function.

[Uzaaft]

1. I think overriding the neo-tree default is a no-go. @AstroNvim/astrocommunity-maintainers Any ideas?
2. Similar to other reviews: Lets use the same method for mappings as we do most of the other plugins.

[mehalter]

I agree not to override default neo-tree operator

[mehalter]

I will take over this PR and get it ready for merge