Feat: lsp support find refs

[amyXia1994]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• N
• Y
  re [Feature] support find reference token list from the definition #712

2. What is the scope of this PR (e.g. component or file name):

added: implement the find reference API and add some integration tests

kclvm/tools/src/LSP/src/find_refs.rs
kclvm/tools/src/LSP/src/test_data/find_refs_test/...

modified:

• add common logic of build word index
• add find reference related lsp provider register, handler
• fix the kcl_pos bug in from_lsp.rs
• update the Definition enum, add a name field in kclvm/tools/src/LSP/src/goto_def.rs and update relative usages of it

kclvm/tools/src/LSP/src/capabilities.rs
kclvm/tools/src/LSP/src/completion.rs
kclvm/tools/src/LSP/src/from_lsp.rs
kclvm/tools/src/LSP/src/goto_def.rs
kclvm/tools/src/LSP/src/hover.rs
kclvm/tools/src/LSP/src/lib.rs
kclvm/tools/src/LSP/src/main.rs
kclvm/tools/src/LSP/src/request.rs
kclvm/tools/src/LSP/src/state.rs
kclvm/tools/src/LSP/src/tests.rs
kclvm/tools/src/LSP/src/util.rs

deleted: the older incomplete implementation attempt about find ref
kclvm/tools/src/LSP/src/find_ref/...

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

Feat: lsp support basic find reference

Known flaws:

• the performance in a large-scaled workspace is slow

• the scope to find references needs to be narrowed down to min(workspace, kcl_package_root). now the find refs searches under the kcl package root(identified by the kcl.mod file)

• does not handle the include_declaration param. now always returns refs include declaration

• the references of an imported package is not supported yet.

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• N
• Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• Unit test
• Integration test
• Benchmark (add benchmark stats below)
• Manual test (add detailed scripts or steps below)
• Other

[coveralls]

Pull Request Test Coverage Report for Build 6493910165

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 87.988%

---

Totals
Change from base Build 6490342979:	0.0%
Covered Lines:	2300
Relevant Lines:	2614

---

💛 - Coveralls

[Peefy]

LGTM