refactor: extract database scripts from creator classes to separate files

[byerlikaya]

🚀 SmartRAG Pull Request

📝 Description

This PR refactors the database setup system by extracting SQL scripts from database creator classes into separate script files. This improves maintainability, follows DRY principles, and makes it easier to manage database initialization scripts.

Key Changes:

• Extracted SQL scripts from ITestDatabaseCreator implementations into separate script files
• Created DatabaseSetup/scripts/ directory for database creation scripts
• Reorganized DatabaseBackups/ directory structure
• Moved large backup files (>100MB) to DatabaseBackups/LargeFiles/ to comply with GitHub file size limits
• Updated .gitignore to exclude large backup files while allowing smaller ones (e.g., salesmanagement.backup.bak)

🔗 Related Issue

N/A - Internal refactoring

🔄 Type of Change

Please mark the relevant options:

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🧪 Test improvements
• 🔧 Code refactoring
• 🚀 Release preparation

🧪 Testing

Please describe the tests that you ran to verify your changes:

• Unit tests pass
• Integration tests pass
• Manual testing completed
• SmartRAG.Demo runs without errors
• Build succeeds with 0 errors, 0 warnings

Testing Details:

• Verified all database creators can successfully create test databases using extracted scripts
• Confirmed SQLite, SQL Server, PostgreSQL, and MySQL database creation works correctly
• Tested database restoration from backup files
• Validated that large backup files are properly excluded from Git

📋 Checklist

• My code follows the SmartRAG style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (EN + TR)
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• LoggerMessage definitions are correct (no parameter mismatches)
• EventId assignments are unique (no conflicts)
• Code is generic and provider-agnostic (no hardcoded domain-specific names)
• All public APIs have XML documentation

🚨 Critical Rules Compliance

• Generic Code: No hardcoded table/database/column names
• Error Fixing: Only fixed the reported error, no refactoring (N/A - this is a refactoring PR)
• Build Quality: 0 errors, 0 warnings, 0 messages
• Language: All code elements in English only
• SOLID/DRY: Principles followed (extracted scripts to eliminate duplication)

📸 Screenshots (if applicable)

N/A

📋 Additional Context

File Structure Changes:

• DatabaseSetup/scripts/ - Contains database creation SQL scripts for all providers
• DatabaseBackups/ - Contains backup files for test database restoration
• DatabaseBackups/LargeFiles/ - Contains large backup files (>100MB) excluded from Git

Script Files Created:

• DatabaseSetup/scripts/create_sqlite_database.sql
• DatabaseSetup/scripts/create_sqlserver_database.sql
• DatabaseSetup/scripts/create_postgresql_database.sql
• DatabaseSetup/scripts/create_mysql_database.sql

Benefits:

• Improved maintainability: SQL scripts are now in separate files, easier to edit and review
• Better organization: Scripts and backups are in dedicated directories
• DRY compliance: No duplicate SQL code in creator classes
• GitHub compliance: Large files are properly excluded

🔄 Migration Guide (if breaking changes)

N/A - No breaking changes. This is a refactoring that maintains backward compatibility.

📊 Performance Impact

• No performance impact
• Performance improvement
• Performance regression (explain below)

Note: This refactoring does not change runtime behavior, only improves code organization.

🔒 Security Considerations

• No security implications
• Security improvement
• Security concern (explain below)

---

Reviewer Guidelines:

• Check for generic, provider-agnostic code
• Verify LoggerMessage parameter counts match format strings
• Ensure EventId assignments are unique
• Confirm 0 errors, 0 warnings build
• Validate documentation updates (EN + TR)

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}