feat: support backtrace in runtime

[NeverRaR]

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

• N
• Y

Close #525

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

KCLVM/kclvm/runtime
kclvm/compiler/src/codegen/

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

feat: support backtrace in runtime

When a runtime error occurs, if the debug parameter is enabled, the compiler will track the backtrace and display,
e.g. If we try to compile the following kcl file,

import math

schema Fib:
    n1 = n - 1
    n2 = n1 - 1
    n: int
    value: int

    if n <= 1:
        value = math.log()
    elif n == 2:
        value = 1
    else:
        value = Fib {n = n1}.value + Fib {n = n2}.value


fib8 = Fib {n = 8}.value

then, we will get

KCLVM % kclvm_cli run --debug ./samples/hello.k           
error[E3M38]: error[E3M38]: EvaluationError
  --> /Users/neverrar/Projects/github/KCLVM/samples/hello.k:10:1
   |
10 |         value = math.log()
   |  log() takes exactly one argument (0 given)
   |
note: backtrace:
        0: kclvm_math_log
                at hello.k:10
        1: __main__.Fib
                at hello.k:10
        2: __main__.Fib
                at hello.k:14
        3: __main__.Fib
                at hello.k:14
        4: __main__.Fib
                at hello.k:14
        5: __main__.Fib
                at hello.k:14
        6: __main__.Fib
                at hello.k:14
        7: __main__.Fib
                at hello.k:14
        8: kclvm_main
                at hello.k:17

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 4783070781

• 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 4751693604:	0.0%
Covered Lines:	2300
Relevant Lines:	2614

---

💛 - Coveralls

[Peefy]

LGTM