Feat: massive changes to definition of components

This change switches back to the original `ctx<props>` syntax for
commponents. This lets lifetime elision to remove the need to match
exactly which lifetime (props or ctx) gets  carried to the output. As
such, `Props` is currently required to be static. It *is* possible to
loosen this restriction, and will be done in the future, though only
through adding metadata about the props through the Props derive
macro. Implementing the IS_STATIC trait is unsafe, so the derive macro
will do it through some heuristics.

For now, this unlocks sharing vnodes from parents to children, enabling
pass-thru components, fragments, portals, etc.

packages/web/examples/demoday.rs

@@ -6,7 +6,7 @@ fn main() {
     wasm_bindgen_futures::spawn_local(WebsysRenderer::start(App))
 }
 
-fn App(ctx: Context, props: &()) -> DomTree {
+fn App(ctx: Context<()>) -> VNode {
     ctx.render(rsx! {
         main { class: "dark:bg-gray-800 bg-white relative h-screen"
             NavBar {}
@@ -15,7 +15,7 @@ fn App(ctx: Context, props: &()) -> DomTree {
     })
 }
 
-fn NavBar(ctx: Context, props: &()) -> DomTree {
+fn NavBar(ctx: Context<()>) -> VNode {
     ctx.render(rsx!{
         header { class: "h-24 sm:h-32 flex items-center z-30 w-full"
             div { class: "container mx-auto px-6 flex items-center justify-between"
@@ -55,7 +55,7 @@ fn NavBar(ctx: Context, props: &()) -> DomTree {
     })
 }
 
-fn Landing(ctx: Context, props: &()) -> DomTree {
+fn Landing(ctx: Context<()>) -> VNode {
     ctx.render(rsx!{
         div { class: "bg-white dark:bg-gray-800 flex relative z-20 items-center"
             div { class: "container mx-auto px-6 flex flex-col justify-between items-center relative py-8"