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/src/debug_renderer.rs

@@ -15,7 +15,7 @@ impl DebugRenderer {
     ///
     /// This means that the root component must either consumes its own context, or statics are used to generate the page.
     /// The root component can access things like routing in its context.
-    pub fn new(root: impl for<'a> Fn(Context<'a>, &'a ()) -> DomTree + 'static) -> Self {
+    pub fn new(root: impl for<'a> Fn(Context<'a, ()>) -> VNode + 'static) -> Self {
         Self::new_with_props(root, ())
     }
 
@@ -24,7 +24,7 @@ impl DebugRenderer {
     ///
     /// A VDom is automatically created. If you want more granular control of the VDom, use `from_vdom`
     pub fn new_with_props<T: Properties + 'static>(
-        root: impl for<'a> Fn(Context<'a>, &'a T) -> DomTree + 'static,
+        root: impl for<'a> Fn(Context<'a, T>) -> VNode + 'static,
         root_props: T,
     ) -> Self {
         Self::from_vdom(VirtualDom::new_with_props(root, root_props))
@@ -78,7 +78,7 @@ mod tests {
 
     #[test]
     fn ensure_creation() -> Result<(), ()> {
-        // static Example: FC<()> = |ctx, props| {
+        // static Example: FC<()> = |ctx| {
         //     //
         //     ctx.render(html! { <div> "hello world" </div> })
         // };