feat: inline dioxus-native from blitz

[jkelleyrtp]

This PR inlines the commits from the blitz repo for the dioxus-native project.

• Migrate package over
• asset resolver
• dx support
• document support
• history support

It also makes dx work native.

If we want to publish 0.6.3, we will need to disable this integration, but I'm assuming we're mostly done with the 0.6 patch cycle. Alternatively, we could publish blitz and then release dioxus-native under a minor release (0.6.3 / 0.6.4, etc). We would just need to commit to the "native" feature flag for the time being.

For feature-flag resolution, we use the named feature flags in the users cargo.toml for platform selection:

[dependencies]
dioxus = { features = ["fullstack"] }

[features]
default = []
desktop = ["dioxus/desktop"]
mobile = ["dioxus/mobile"]
web = ["dioxus/web"]
server = ["dioxus/server"]

This means to use the new native renderer, you would simply migrate the desktop and mobile renderers over:

[features]
default = []
desktop = ["dioxus/native"]
mobile = ["dioxus/native"]
web = ["dioxus/web"]
server = ["dioxus/server"]

[jkelleyrtp]

asset resolver works!

[jkelleyrtp]

dx serve also works

[nicoburns]

For feature-flag resolution, we use the named feature flags in the users cargo.toml for platform selection:
This means to use the new native renderer, you would simply migrate the desktop and mobile renderers over:

With the current code, is it possible to setup feature flags so that you can have both "webview" and "blitz" versions of an app (with different feature flags)?

[nicoburns]

Moving the crate here will mean that we wont be able to easily run dioxus-native-based examples from the Blitz repository. Is the idea is that we would move any relevant examples here? Most of them were based on dioxus examples in the first place, but we might want to check that the unmodified examples work with the native renderer, and port some of the blitz examples that are just testing rendering features to the html renderer?