Disable the map_unwrap_or lint

[abey79]

What

map_or(default_value, |val| f(val)) is imo strictly worse than map(|val| f(val)).unwrap_or(default_value), especially in a context of chained calls where having each on a different line is better. So this PR disables this lint.

Relevant slack thread: https://rerunio.slack.com/archives/C0440MD5UAV/p1724749276769059

Arguably, the self-admitted known limitations are much worse than the supposed problem this lint is supposed to fix: https://rust-lang.github.io/rust-clippy/stable/index.html#/map_unwrap_or

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]

I like the brevity of map_or, but I also think it’s weirdly backwards - it says “map, or” but then does the opposite.

As long as you don’t plan on aggressively changing stuff back :D ✅

[abey79]

No war against map_or. If it avoids a line break, fine 🤷🏻 I just want clippy to leave me alone with my map().unwrap_or() :)