chore: config isort known_third_party to fix import formatting errors

[Jay-ju]

Changes Made

When I develop the connectors for daft and lance simultaneously, I debug the code in the same venv environment. At this time, it seems that when formatting, lance is regarded as daft's own implementation. So, I've clarified the isort rules for formatting here.

This PR Before:

This PR After:

Related Issues

Checklist

• Documented in API Docs (if applicable)
• Documented in User Guide (if applicable)
• If adding a new documentation page, doc is added to docs/mkdocs.yml navigation
• Documentation builds and is formatted properly (tag @/ccmao1130 for docs review)

[greptile-apps]

Greptile Summary

This PR adds explicit import sorting configuration to the .ruff.toml file to resolve formatting inconsistencies when developing Daft and Lance packages simultaneously. The change adds two new lines to the [tool.ruff.lint.isort] section: known-first-party = ["daft"] and known-third-party = ["lance"].

The issue arises because when both Daft and Lance are installed in the same development environment, the isort tool (used by Ruff for import formatting) can become confused about whether Lance imports should be treated as first-party (internal to the project) or third-party (external dependencies). Without explicit configuration, isort may incorrectly group Lance imports with Daft's own modules, leading to inconsistent import ordering.

This configuration change integrates well with Daft's existing code quality infrastructure. The repository already uses Ruff for linting and formatting (as evidenced by the existing .ruff.toml configuration file), and this change simply extends that configuration to handle edge cases in import sorting. The fix follows standard Python development practices for managing import organization in projects that work closely with related packages.

Confidence score: 5/5

• This is an extremely safe change that only affects code formatting and has zero functional impact
• The configuration follows standard isort practices and addresses a legitimate development workflow issue
• No files need additional attention as this is a simple configuration change

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.55%. Comparing base (6ef8e52) to head (f6a6e3a).
⚠️ Report is 44 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4840      +/-   ##
==========================================
- Coverage   78.84%   78.55%   -0.29%     
==========================================
  Files         890      890              
  Lines      123743   123945     +202     
==========================================
- Hits        97559    97364     -195     
- Misses      26184    26581     +397     

see 23 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.