fix(deps): replace snowflake-sql-api git URL with PyPI version pin

[hampsterx]

Summary

• PyPI rejects package metadata containing direct-URL (@ git+https) dependencies. This blocked the 1.4.0 publish: the build succeeded but upload returned 400 Can't have direct dependency: snowflake-sql-api @ ..., so 1.4.0 (including the new [llm] helper) never reached PyPI.
• snowflake-sql-api is now published on PyPI (0.1.1), so it can be pinned as a normal version requirement.
• Replaces the git reference with snowflake-sql-api>=0.1.1,<0.2.0 in the snowflake and dev extras, across both setup.py and pyproject.toml. The two files had drifted (only pyproject's dev extra carried the git dep); they are consistent now.

Context

This was a pre-existing packaging bug introduced with the snowflake extra (PR #27), not the LLM helper (PR #28). 1.3.3 had no snowflake extra, so it published fine; 1.4.0 was the first release to carry the direct-URL dep in its metadata. A new tag (1.4.1) is needed to re-attempt publish after this merges.

Test plan

• python -m build succeeds (wheel + sdist)
• twine check dist/* passes
• Built wheel METADATA has no direct-URL Requires-Dist entries; snowflake-sql-api shows Requires-Dist: snowflake-sql-api<0.2.0,>=0.1.1; extra == "snowflake" (and dev)
• Tag 1.4.1 after merge, confirm the publish workflow uploads to PyPI

[coderabbitai]

Warning

Review limit reached

@hampsterx, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 25 minutes and 23 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 096e6c09-7d3b-4e54-a557-8e61ec7ad2e7

📥 Commits

Reviewing files that changed from the base of the PR and between fed8296 and e8968ca.

📒 Files selected for processing (2)

• pyproject.toml
• setup.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/snowflake-sql-api-pin

---

_{Comment @coderabbitai help to get the list of available commands.}