feat: add database-driven material validation with multi-mode support

This commit enhances the material validation functionality to support
database-driven workflows alongside the existing Excel-based approach.

## New Features

### DAO Layer
- Add ProductionContractDataDAO for querying production contract data
- Add MaterialsToBeDeletedDAO with full CRUD operations
- Enhance DiscreteMaterialPlanDAO with query_all(), query_by_source_numbers(),
  and get_unique_material_names() methods

### Validation Modes
Support for 4 validation modes in MaterialValidationTab:
1. Database Full - Query all materials from DiscreteMaterialPlanData
2. Database Filtered - Query by ProductionID.txt file
3. Excel Existing - Validate from existing Excel file
4. Excel Full - Complete workflow with ERP extraction

### Configuration
- Add ValidationConfig dataclass with data_source, batch_size, match_mode,
  enable_crud_operations, and default_manager fields
- Update ConfigLoader to support validation configuration
- Add validation settings section in SettingsTab GUI

### Query Chain
Implementation of full query chain:
ProductionID.txt (总排号) → productionContractData (生产订单号) →
DiscreteMaterialPlanData (SourceNumber) → MaterialName →
MaterialsToBeDeleted comparison

## Backward Compatibility
All existing Excel-based validation methods remain unchanged, ensuring
no breaking changes for existing workflows.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

config/defaults.py

@@ -10,6 +10,7 @@ from config.schema import (
     DatabaseConfig,
     PathConfig,
     ExtractionConfig,
+    ValidationConfig,
     AppConfig,
 )
 
@@ -45,6 +46,14 @@ DEFAULT_APP_CONFIG = AppConfig(
         merge_batches=True,
         enable_db_persistence=False,  # Disabled by default
     ),
+    validation=ValidationConfig(
+        data_source="database_full",
+        use_database=True,
+        batch_size=2000,
+        enable_crud_operations=False,
+        default_manager="",
+        match_mode="substring",
+    ),
 )