Don't arbitrarily constrain dependency versions

[mrcljx]

Description

For libraries, the best practice is to only list known incompatibilities and not potential future incompatibilities. Using <= (or ~=) constraints can:

• Lead to dependency resolution conflicts for downstream consumers
• Prevent users from using newer versions of dependencies that are likely still compatible
• Reduce composability in larger environments or monorepos

Note how pydantic itself has no <= constraints. You'll find the same with other libraries.

[nicknisi]

Thanks, @mrcljx!