* docs: clarify difference between use_context and consume_context
Document the key distinction: use_context is a hook that captures the
context value once on first render and caches it, following the rules
of hooks. consume_context reads directly from the runtime each time
and can be called from anywhere (event handlers, async tasks, etc.).
Fixes#3862
* fix: remove redundant explicit rustdoc link targets
* fix: use plain text for cross-crate use_context reference in rustdoc
Improve inline docs
* improve incorrect event handler return error message
* Improve event handler docs
* document the eval functions
* document spawn and common spawn errors
* fix event handler docs
* add notes about how you use attributes and elements in rsx
* add doc aliases for attributes and events we rename
* add some more aliases for common search terms
* don't doc ignore any public examples in core
* don't ignore public doc examples in ssr
* don't ignore examples in the dioxus package readme
* add a warning when you launch without a renderer enabled
* fix some outdated element docs
* add a bunch of examples to resource
* add notes about desktop events
* add more docs for use_resource
* add on_unimplemented hint to Dependency
* fix some unresolved links
* add examples to each of the router traits
* add not implemented errors for router traits
* add an example to the routable trait
* expand rsx macro docs
* improve memo docs
* update the dioxus readme
* mention dioxus crate features in the docs
* fix a bunch of doc tests
* fix html doc tests
* fix router doc tests
* fix dioxus signals doc tests
* fix dioxus ssr doc tests
* fix use_future example in the hooks cheat sheet
* add a javascript alias for eval
* fix hook explanation values
* remove unused embed-doc-image dependency
John Costa