[WIP] Feat(LSP): Semamtic token provider (#297)

[He1pa]

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

• N
• Y [Feature][Design] Design and Implementation of a General LSP Server Based on Rust #297

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

LSP Server

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

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

Add semantic token provider to LSP Server, used to semantic highlight

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

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[coveralls]

Pull Request Test Coverage Report for Build 4313896503

• 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 90.562%

---

Totals
Change from base Build 4310888046:	0.0%
Covered Lines:	1612
Relevant Lines:	1780

---

💛 - Coveralls

[Peefy]

s/test_resolve_program/test_imcomplete_semantic_tokens

[Peefy]

1. I suggest that like the KCL dependency analysis tool, this is the same for LSP. First, establish a Virtual File System (VFS), and build an overall workspace in the system through a monitor. Secondly, collect all compilation units according to kcl.yaml files lazily and detect file modification behaviors such as adding, deleting, and modifying files. Ref: [Enhancement][Track] A better KCL compiler frontend technology architecture for the LSP tool and IDE extensions #420 and https://github.com/KusionStack/kclvm-go/blob/main/pkg/tools/list/dep_parser.go#L52
2. You MUST avoid calling the unwrap() function in server code and using Result to deal errors.