Tracking: `ibis` typing fixes

[dangotbanned]

Aiming to collect issues we've had, with the hope to make some small suggestions upstream and make our type checkers happier 😅

Code Search

Should be most of the individual cases, but ideally we could pull out some common issues from here

• Using typing.cast
• Using # (type|pyright): ignore
• Using : Any

Comments

• feat: IbisLazyFrame support #2000 (comment)
• chore: fixup operator type ignores for SQLExpr #2920 (comment)
• fix: Align division by zero behavior across all backends #2761 (comment)
• TYP: Use ibis.Deferred instead of ibis.Value for typing #2963 (comment)

PRs

• fix(typing): Add overloads for ibis lit #2972

Upstream

• feat: Improve VSCode experience (type hints, docs, etc) ibis-project/ibis#11680
• feat(typing): make types more precise for many common Values ibis-project/ibis#11771
• bug: incorrect typing for Table.filter ibis-project/ibis#11667
• bug: Incomplete type hint in Table.select, omits s.Selector ibis-project/ibis#11511
• bug: IntervalValue property annotations do not match the actual return type of as_unit ibis-project/ibis#11302
• feat: improve typing for ibis.<backend>.connect() ibis-project/ibis#11188
• feat: Intellisense for the underscore table accessor ibis-project/ibis#10369

[dangotbanned]

@FBruzzesi, @MarcoGorelli

It seems like I'm viewing the use of operators as less important when they can be worked around (#2920 (comment))

I'm happy to concede on this and make getting operator-typing working for ibis the first goal here 🙂

This is a pretty minimal repro to get us started:

import ibis

>>> ibis.literal(1) / ibis.literal(2)   # Operator "/" not supported for types "Scalar" and "Scalar"
Divide(1, 2): 1 / 2