Feat: lsp support complete for docstring

[amyXia1994]

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

• N
• Y
  close [Feature] docstring generating and auto-completing in LSP #709

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

record ast node for doc in schema_stmt/rule_stmt/module:

• kclvm/ast/src/ast.rs
• kclvm/ast/src/tests.rs
• kclvm/ast_pretty/src/node.rs
• kclvm/parser/src/parser/module.rs
• kclvm/parser/src/parser/stmt.rs
• kclvm/sema/src/resolver/doc.rs
• kclvm/sema/src/resolver/global.rs

snapshot update due to added doc node:

• kclvm/parser/src/tests/snapshots/

docstring generation:

• kclvm/sema/src/resolver/doc.rs

autocomplete on newline within empty docstring:

• kclvm/tools/src/LSP/src/completion.rs
• kclvm/tools/src/LSP/src/util.rs
• kclvm/tools/src/LSP/src/test_data/completion_test/newline/docstring_newline.k

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

support auto-complete on newline within empty docstring

• 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 6715050969

• 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.82%

---

Totals
Change from base Build 6704930171:	0.0%
Covered Lines:	2300
Relevant Lines:	2619

---

💛 - Coveralls

[Peefy]

LGTM