fix: refactor if-statement codegen and enhance test runner

[LunaStev]

This PR addresses critical issues in the code generation logic for if statements and significantly upgrades the integration testing infrastructure. The changes ensure that control flow is generated correctly for complex conditional chains and that the automated test suite can handle networking and interactive scenarios without manual intervention.

Key Changes

1. Robust If Statement Codegen

• Automatic Type Coercion: Implemented a conversion layer that transforms Integers, Floats, and Pointers into i1 (boolean) types. This allows the Wave compiler to support C-style truthiness (e.g., if (pointer)) while satisfying LLVM's strict branching requirements.
• Control Flow structural Fix:
  • Reorganized else if and else BasicBlock generation to ensure correct linear ordering in the IR.
  • Fixed termination logic where certain code paths would previously fail to branch to the merge block, leading to "terminator found in the middle of a block" errors.
• Reliable Branching: Ensured every conditional path properly ends with a jump to the final merge point, preventing IR validation failures.

2. Test Runner (run_tests.py) Enhancements

• UDP Support for Networking Tests: Added a background threading mechanism to send a UDP packet specifically during test61.wave. This allows the network listener test to receive data and exit successfully instead of hanging until a timeout.
• Interactive Test Skipping: Introduced a SKIP status for tests that require manual user input (e.g., test22.wave for input() verification). This prevents the CI/CD pipeline from reporting false-positive failures for tests that cannot be fully automated.
• Improved Reporting: Updated the terminal output and final summary to clearly distinguish between Passed, Failed, and Skipped tests.

3. Maintenance

• GitHub Config: Cleaned up the repository configuration by removing the custom link from .github/FUNDING.yml.

Examples of Improved Codegen Behavior

// Now correctly coerced to i1 in LLVM IR
var p: ptr<i32> = ...;
if (p) { 
    // executes if p is not null
}

var count: i32 = 10;
if (count) {
    // executes if count != 0
}

Benefits

• Correctness: Fixes invalid IR generation for nested or chained conditional blocks.
• Developer Experience: The test runner is now "greener" by correctly handling edge-case tests (networking/interactive).
• Standard Compliance: Brings if condition behavior closer to industry standards (C/C++, Rust).