Move re_renderer examples to its own crate in order to make workspace level examples less confusing

[Wumpf]

What

This way we don't show renderer examples like "the examples". Also, due to some dependency issues with the optional re_renderer arrow dependency (details somewhat unclear..), we were previously no longer able to run examples on the web. This works nicely now again:

depicted:

• cargo run -p re_renderer_examples --bin multiview (native)
• cargo run-wasm -p re_renderer_examples --bin multiview --features "webgl" (webgl, using firefox here)
• cargo run-wasm -p re_renderer_examples --bin multiview (webgpu, using chrome here)

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):
  • Full build: app.rerun.io
  • Partial build: app.rerun.io - Useful for quick testing when changes do not affect examples in any way
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

• PR Build Summary
• Docs preview
• Examples preview
• Recent benchmark results
• Wasm size tracking

[teh-cmc]

Oh man I completely forgot about these; the memories 🥲

Anyway, looks nice! Here's a crazy idea though: can we move re_renderer_examples under re_renderer?
As in, it would still be an independent crate, with a cargo name of re_renderer_examples but a repo/filesystem name of re_renderer/examples?

[teh-cmc]

Hmm, what's this?

[Wumpf]

our ci wants now all crates to be listed here, but I figured that's a weird one to list. So I pretend list it!

[Wumpf]

As in, it would still be an independent crate, with a cargo name of re_renderer_examples but a repo/filesystem name of re_renderer/examples?

👍 I'll try that! Not sure if cargo gets confused by this

[Wumpf]

tried and Cargo doesn't like it at all. We figured it's time to directorify crates, not happening in this PR though.