refactor: compiling kcl code to object file instead of dylib and packaging LLVM lld library statically into kclvm binary.

[Peefy]

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

• N
• Y

re #53.

In order to better package KCLVM and reduce the probability of errors in the user's local kcl binary, the llvm library is statically packaged into the kcl binary to avoid using the user's local clang for assembling and linking. The goal is to solve the instability problem when KCL uses the user's clang/ld for code linking (mainly due to different versions of built-in cc on different OS).

Besides, after solving this problem, it is necessary to further move the python3 included in the KCLM from the KCLVM installation package to the outside to reduce the final KCLVM installation package size. cc @chai2010

Design

The previous compilation process is:

After the issue is completed, the KCLVM binary package only contains the following contents (Take the macos target as an example, and the size is ~80M-90M):

• kclvm_cli # KCLVM Rust CLI (using kc run or kpm run later.)
• libkclvm_native.dylib # KCLVM Runtime native Lib for native targets including macos, linux and windows target.
• libkclvm_wasm32.dylib # KCLVM WASM32 lib for the WASM target.

Note:

• Support targets: mac-x86, mac-arm, linux-x86 target.
• TODO targets: windows, linux-arm WASM target.

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

• kclvm_compiler crate.
• kclvm_runner crate.

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

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

• Including all grammar and unit test suites.
• Add macos github runners on macos10, macos11, macos12.

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 3407067403

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

---

Totals
Change from base Build 3390800496:	0.0%
Covered Lines:	1369
Relevant Lines:	1526

---

💛 - Coveralls

[ldxdl]

lgtm

[zong-zhe]

LGTM