release: publish dioxus-native at 0.7.3, against the 0.4 engine

[pathscale]

The 0.4.0 release moved every published engine crate but left ps-dioxus-native and ps-dioxus-native-dom behind.

Their manifests on master are already correct — the engine arrives through workspace = true, which is ^0.4.0. The problem is the registry: 0.7.2 is what is published, and 0.7.2 went out carrying ^0.3.0-beta.6. A published version cannot be corrected in place, so this is a new version rather than a re-release.

Why it matters

The symptom is not a stale renderer. It is two engines.

A crate that takes ps-blitz ^0.4 and dioxus-native ^0.7.2 resolves both 0.4.0 and 0.3.0-beta.6. Cargo treats them as unrelated crates that happen to export the same names:

expected `blitz_script::document::ScriptDocument`, found `ScriptDocument`

with both types pointing at the same file.

Measured

Resolving chuzz against ps-blitz ^0.4 with the published dioxus-native gives a graph carrying both lines:

ps-blitz-dom     ['0.3.0-beta.6', '0.4.0']
ps-blitz-net     ['0.3.0-beta.6', '0.4.0']
ps-blitz-paint   ['0.3.0-beta.6', '0.4.0']
ps-blitz-shell   ['0.3.0-beta.6', '0.4.0']
ps-blitz-traits  ['0.3.0-beta.6', '0.4.0']
ps-stylo-taffy   ['0.3.0-beta.6', '0.4.0']

Every beta edge traces back to ps-dioxus-native 0.7.2 and ps-dioxus-native-dom 0.7.2; nothing else in the graph asks for the beta line.

With these two patched to this branch, the same resolve produces one copy of each and no patch ... was not used warning.

Verified

cargo metadata on this branch reports the requirements these crates will publish with:

== ps-dioxus-native 0.7.3        == ps-dioxus-native-dom 0.7.3
   ps-blitz-dom     ^0.4.0          ps-blitz-dom     ^0.4.0
   ps-blitz-html    ^0.4.0          ps-blitz-traits  ^0.4.0
   ps-blitz-net     ^0.4.0
   ps-blitz-paint   ^0.4.0
   ps-blitz-shell   ^0.4.0
   ps-blitz-traits  ^0.4.0

Blocks

chuzz cannot land its 0.4 pin bump until this is on the registry.

No code changes — only the version these two crates claim and the workspace ranges naming them.

[pathscale]

Superseded by #83, which stacks all three into one PR with the 0.4.1 workspace bump.