feat: add SQL Server database persistence for extracted material plan data

Add optional database persistence feature that automatically saves extracted
discrete material plan data to SQL Server. Users can enable this feature in
the settings tab.

Changes:
- Add enable_db_persistence flag to ExtractionConfig (default: disabled)
- Create DiscreteMaterialPlanDAO for database operations with REPLACE pattern
- Update progress tracking to include database persistence stage (90-100%)
- Add database persistence checkbox in settings UI
- Remove verbose logging checkbox from data extraction UI (config-only now)
- Update extraction workflow to save merged DataFrame to database

Progress weights adjusted:
- download: 65% -> 60%
- database: 10% (new stage)
- Other stages adjusted accordingly

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

config/schema.py

@@ -85,6 +85,7 @@ class ExtractionConfig:
     verbose: bool = True
     auto_convert: bool = True
     merge_batches: bool = True
+    enable_db_persistence: bool = False
 
     def validate(self) -> list[str]:
         """验证配置，返回错误列表"""
@@ -144,5 +145,6 @@ class AppConfig:
                 "verbose": self.extraction.verbose,
                 "auto_convert": self.extraction.auto_convert,
                 "merge_batches": self.extraction.merge_batches,
+                "enable_db_persistence": self.extraction.enable_db_persistence,
             },
         }