fix(refactoring-nvim): fix dependencies and API usage for latest version

[rami3l]

📑 Description

The last update of this bundle is from more than 1 year ago, and both the dependencies and the APIs have changed quite a bit since then.

📖 Additional Information

See https://github.com/ThePrimeagen/refactoring.nvim#configuration for the example keymapping config.

Personally I would actually prefer having the users configure the keymap themselves for this plugin with rather rich functionalities... @Uzaaft what do you think?

[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)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

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

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

[Uzaaft]

I just looked at the rewrite.
Holy fuck is that a sloppy rewrite.

I think we should keep the keymaps in here. astrocommunity is meant to cover both power users and people who just want a OOTB experience.

@rami3l

[rami3l]

I think we should keep the keymaps in here. astrocommunity is meant to cover both power users and people who just want a OOTB experience.

@Uzaaft Sure!

I just looked at the rewrite.

is that a sloppy rewrite.

You mean the recent rewrite of the refactoring plugin in question? Yup I was quite surprised when it requires expr = true among other stuff :|