fix: enable checkpoints for SQL files

[roomote]

Description

This PR attempts to address Issue #7310. Feedback and guidance are welcome.

Problem

Users reported that checkpoint functionality (diff/restore) was disabled for .sql files. When they changed the file extension to .py, checkpoints worked correctly.

Solution

Removed *.sql from the database file exclusion patterns in the checkpoint service. SQL script files that users are actively working on should be eligible for checkpoint operations.

Changes

• Removed *.sql from getDatabaseFilePatterns() in src/services/checkpoints/excludes.ts
• Added test coverage to verify SQL files are no longer excluded from checkpoints

Testing

• ✅ All existing tests pass
• ✅ Added specific test assertions to verify SQL files are not excluded
• ✅ Ran checkpoint service tests successfully

Impact

Users will now be able to:

• Use checkpoint diff functionality with .sql files
• Restore checkpoints for SQL files
• Have the same checkpoint experience with SQL files as with other code files

Fixes #7310

---

Important

Enables checkpoint functionality for .sql files by removing them from exclusion patterns, fixing issue #7310.

• Behavior:
  • Enables checkpoint functionality for .sql files by removing *.sql from exclusion patterns in getDatabaseFilePatterns() in excludes.ts.
  • Users can now use checkpoint diff and restore functionalities with .sql files.
• Testing:
  • Updated excludes.spec.ts to verify .sql files are not excluded from checkpoints.
  • Added assertions to ensure .sql files are included in checkpoint operations.
• Impact:
  • Aligns .sql file behavior with other code files for checkpoint operations.
  • Fixes issue checkpoint is disabled with .sql #7310.

^{This description was created by for 71e93f3. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Reviewing my own code is like debugging in production - technically possible but morally questionable.

[roomote]

Good fix! Removing SQL files from exclusions makes sense since they're text-based scripts users actively edit. However, two considerations:

1. Large SQL dumps: Some SQL files can be multi-gigabyte database dumps. Users should add these to .gitignore if needed.

2. CSV consistency: I noticed CSV files (*.csv) are still excluded in this list, but they're also text files users might edit. Should we consider removing CSV from exclusions for consistency?

3. Documentation: Consider adding a comment above getDatabaseFilePatterns() explaining it excludes binary database files but not SQL scripts.

[daniel-lxs]

After reviewing this change, I need to reject it. SQL files were excluded from checkpoints for good reason - they can become extremely large (database dumps, migration scripts with seed data, etc.) and would significantly impact checkpoint performance. The exclusion pattern exists to protect the checkpoint system from these potentially massive files.

The current behavior is intentional and should be maintained. I'll close this PR and provide more context on the issue.

[daniel-lxs]

Closing this PR as SQL files should remain excluded from checkpoints due to performance considerations.