fix(refactoring-nvim): improve lazy loading

[Subjective]

No description provided.

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

[owittek]

LGTM!

[owittek]

Ah, almost missed it! Please edit the commit message to use the proper scope: fix(editing-support)

[Subjective]

Wait shouldn't it be fix(refactoring-nvim) as per the Review Checklist?

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

[owittek]

Wait shouldn't it be fix(refactoring-nvim) as per the Review Checklist?

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

Actually you're right, not sure why the pipeline failed before. And I am too sleepy to tell that it wasn't an error on your side. Sorry!

[Subjective]

Oh no, it's because I just changed the name of the PR, it was actually just fix(refactoring) before