Fix Failing Rust Analysis Integration Tests

[milliondreams]

Priority: P1 - Critical Bug Fix

Description:
Two Rust integration tests are currently failing, indicating incomplete implementation of advanced Rust analysis features.

Failing Tests:

• test_enhanced_rust_analysis_concurrency_issues - assertion failed: has_deadlock_potential
• test_severity_and_impact_levels - Should have medium impact performance issues

Root Cause:
The Rust analysis implementation may not be correctly detecting all concurrency issues and performance impact levels as expected by the tests.

Requirements:

• Fix deadlock potential detection in concurrency analysis
• Ensure performance impact levels are correctly assessed
• Verify test expectations align with actual analysis capabilities
• Update analysis logic or test cases as needed

Acceptance Criteria:

• All Rust integration tests pass
• Concurrency analysis correctly identifies deadlock potential scenarios
• Performance analysis assigns appropriate impact levels
• No regression in existing working tests

Technical Notes:

• Check crates/codeprism-lang-rust/src/analysis.rs concurrency analysis methods
• Review crates/codeprism-lang-rust/tests/integration_tests.rs test expectations
• Verify analysis patterns match test code inputs

Estimated Timeline: 1 week

[milliondreams]

Solution Approach for Issue #63

Problem Analysis:
Two failing Rust integration tests indicate incomplete analysis implementation:

1. test_enhanced_rust_analysis_concurrency_issues - assertion failed: has_deadlock_potential
2. test_severity_and_impact_levels - Should have medium impact performance issues

Investigation Plan:

1. Run the failing tests to see exact error messages
2. Examine current analysis.rs implementation vs test expectations
3. Check if analysis logic correctly identifies concurrency and performance patterns
4. Update implementation or test expectations as needed

Implementation Strategy:

1. Phase 1: Diagnose failing tests and understand expected behavior
2. Phase 2: Fix concurrency analysis deadlock detection
3. Phase 3: Fix performance impact level assessment
4. Phase 4: Ensure no regressions in existing functionality

Technical Approach:

• Focus on crates/codeprism-lang-rust/src/analysis.rs concurrency methods
• Review crates/codeprism-lang-rust/tests/integration_tests.rs test cases
• Ensure analysis patterns correctly match test input code
• Validate that severity classification aligns with expected impact levels

Starting implementation now.