Upgrade dioxus to 0.7.6 and switch to dioxus-logger

[esimkowitz]

Summary

• Bump dioxus from 0.7.5 to 0.7.6 (the rest of the ecosystem crates were already resolved at 0.7.6 transitively)
• Replace the unmaintained wasm-logger crate and the custom SimpleLogger with dioxus-logger (enabled via the logger feature on dioxus)
• Update all log:: calls to tracing:: calls

Test plan

• cargo check --features desktop
• cargo check --features web --target wasm32-unknown-unknown --no-default-features
• cargo clippy --all-targets -- -D clippy::style -D clippy::complexity -D clippy::perf
• npm run format:check
• Smoke test npm run serve:desktop and confirm log output appears
• Smoke test npm run serve:web and confirm browser console logs appear

🤖 Generated with Claude Code

---

Note

Medium Risk
Moderate risk due to swapping the logging backend across both desktop and wasm builds and bumping dioxus, which could change runtime initialization and log output behavior.

Overview
Upgrades dioxus from 0.7.5 to 0.7.6 and enables its logger feature.

Removes the custom src/logger implementation and the wasm-logger dependency, initializing logging via dioxus::logger::init in main and switching callsites from log::* macros to tracing::*.

Updates Cargo features so web no longer pulls in wasm-logger, and refreshes Cargo.lock accordingly.

^{Reviewed by Cursor Bugbot for commit 00c0af6. Bugbot is set up for automated code reviews on this repo. Configure here.}