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/core/examples/contextapi.rs

@@ -10,19 +10,20 @@ struct Props {
 }
 
 #[allow(unused)]
-static Example: FC<Props> = |ctx, props| {
+static Example: FC<Props> = |cpt| {
     todo!()
+
     // let value = ctx.use_context(|c: &SomeContext| c.items.last().unwrap());
 
     // ctx.render(LazyNodes::new(move |bump| {
     //     builder::ElementBuilder::new(bump, "button")
     //         .on("click", move |_| {
-    //             println!("Value is {}", props.name);
+    //             println!("Value is {}", ctx.name);
     //             println!("Value is {}", value.as_str());
     //             println!("Value is {}", *value);
     //         })
     //         .on("click", move |_| {
-    //             println!("Value is {}", props.name);
+    //             println!("Value is {}", ctx.name);
     //         })
     //         .finish()
     // }))