Remove the upper bound constraint on python version

[jleibs]

What

We previously had this constraint in place to avoid certain edge cases of users not being able to install Rerun and not understanding why due to transitive deps. Primarily on pyarrow.

I've confirmed pyarrow is now doing something similar in their own project:
https://github.com/apache/arrow/blob/main/python/pyproject.toml#L37

Let's try to let the package solver do the right thing and only add a max-version if we find we are truly incompatible with some future python version.

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using examples from latest main build: rerun.io/viewer
  • Using full set of examples from nightly build: rerun.io/viewer
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
• If applicable, add a new check to the release checklist!
• If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

• PR Build Summary
• Recent benchmark results
• Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

[github-actions]

Deployed docs

Commit	Link
ad233f7	https://landing-3iyh1uep1-rerun.vercel.app/docs

[hgaiser]

Interestingly packages like pytorch don't list an upper limit, even though they are not always compatible with the latest python.

https://github.com/pytorch/pytorch/blob/6e85266a47908c917fe7bcf7d2b837711a1f1cab/setup.py#L1509

pytorch/pytorch#130249