feat: DSL semantic checking analysis

[AlSchlo]

Problem

We want to reject DSL programs that are semantically incorrect. This PR analyzes the parsed AST and rejects if an error is detected.

Summary of changes

• Parser bug fixes
• Implemented SemanticAnalyzer to perform comprehensive static analysis on DSL programs
• Added validation for properties:
  • Ensures property types are valid (basic types, maps, arrays, tuples)
  • Rejects function types and operators in properties
• Added validation for operators:
  • Prevents duplicate operator names
  • Validates field types for both scalar and logical operators
  • Ensures logical operators have all required derived properties
  • Verifies derived properties match declared logical properties
• Added scope-based identifier validation:
  • Maintains a stack of scopes for variable declarations
  • Prevents duplicate identifiers in the same scope
  • Validates variable references exist in accessible scopes
• Added recursive expression validation:
  • Validates all sub-expressions in compound expressions
  • Handles various expression types (variables, function calls, conditionals, etc.)
  • Manages scope for closures and pattern matching
• Added comprehensive test suite:
  • Tests for valid DSL programs
  • Tests for various error conditions (duplicate names, invalid types, etc.)
  • Tests for scope handling and identifier validation

The semantic analyzer provides early error detection for DSL programs, helping users identify issues before runtime.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 95.10086% with 17 lines in your changes missing coverage. Please review.

Project coverage is 80.4%. Comparing base (baa09fc) to head (e5ed19b).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
optd-core/src/dsl/analyzer/semantic.rs	95.0%	17 Missing ⚠️

Additional details and impacted files

Files with missing lines	Coverage Δ
optd-core/src/dsl/parser/expr.rs	86.3% <ø> (ø)
optd-core/src/dsl/parser/functions.rs	90.3% <ø> (ø)
optd-core/src/dsl/parser/mod.rs	96.9% <100.0%> (ø)
optd-core/src/dsl/parser/operators.rs	90.4% <ø> (ø)
optd-core/src/dsl/parser/patterns.rs	83.0% <ø> (ø)
optd-core/src/dsl/parser/types.rs	89.3% <ø> (ø)
optd-core/src/dsl/analyzer/semantic.rs	95.0% <95.0%> (ø)

[skyzh]

generally LGTM

[skyzh]

dup w/ parser/programs?

[skyzh]

To make it user friendly in the future, we probably need to raise the compiler error at the site where the error occurs, for example, Line X Column Y, (something like a source code span could help, pest should support that)

[AlSchlo]

Yes. I was planning to add that in the future. Usually you add that in the AST annotations.