Update futures util (and related) due to yanked crate

[Wumpf]

What

While updating #6795, I noticed that cargo deny warned about our version of futures-utils being yanked. cargo update -p futures-util ran cleanly, no duplicated dependencies as a result

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.

[Wumpf]

ci says:

AssertionError: Some components are missing from the ALL_COMPONENTS dictionary: {'LengthBatch'}

wasn't me 🤷