Reflactor

[jinzhongjia]

I created this plugin just because I needed a stable lsp plugin (didn't follow many specifications), now I want to refactor the logic of the entire code and add new features

Some real-world testing is required before merging

Here are the features I think need to be added：

• [x] declaration 585dcbfb81a253060b8f1b3b66e817c1bbfeb954 - 669c77cee2e3ce1862189760f7032799bca22f43
• [x] definition(not peek definition) 585dcbfb81a253060b8f1b3b66e817c1bbfeb954 - 669c77cee2e3ce1862189760f7032799bca22f43
• [x] type definition 585dcbfb81a253060b8f1b3b66e817c1bbfeb954 - 669c77cee2e3ce1862189760f7032799bca22f43
• [x] implemention 585dcbfb81a253060b8f1b3b66e817c1bbfeb954 - 669c77cee2e3ce1862189760f7032799bca22f43
• [x] reference 585dcbfb81a253060b8f1b3b66e817c1bbfeb954 - 669c77cee2e3ce1862189760f7032799bca22f43
• [x] code lens (Just server support is not enough)
• [x] inlay hint https://github.com/jinzhongjia/LspUI.nvim/pull/22
• [x] callHierarchy https://github.com/jinzhongjia/LspUI.nvim/pull/30
• [x] add dynamic width to secondary

If you can see this issue, you can discuss what features need to be added！！

Features that have been refactored:

• [x] rename eb3f31e9f6e3f35533d379a24a107b563903a294
• [x] lighthulb 949c80dee3040e71cca7f2cba477afb711023a02 - ad82527684c42ca8087d3adfc7290eeddfa65326
• [x] code_action ec0367bb1bd5666ec7cbfa6af42229b37b696a14 - 58f59ced1fe812aed9e97e00160ec1a0f6934cd3
• [x] diagnostic 9915ca2e43efd1d3e7edbed5e80ce96988353f90 - 27538e88e7f3d3000df9ee55dd139c7fdc8a50d6
• [x] hover 9c64a920641d507eb495830eef50d92879447fea - 90a02dc41ff03f4fb2706bb979a00b4e8cc3e772

note:

The following are all completed

code action should provide registration method, for lua's code action diagnostic should provide a diagnostic overview of the current workspace and files

Problems:

the keymap only will remove, we should restore keymap

[jinzhongjia]

Development specification:

1. Each module contains its own init function
2. Create command when module init
3. Each module is decoupled, can be referenced and used separately
4. Each module has func run
5. As neovim is the host system, its plugins should be kept as minimally intrusive as possible

[jinzhongjia]

In feature, maybe some nvim-builtin func need to be rewrite ? such as get next diagnostic, it do repeated operations

[jinzhongjia]

now, I didn't know how to display callHierarchy