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/alternative.rs

@@ -2,7 +2,7 @@ fn main() {}
 
 use dioxus_core::prelude::*;
 
-static Example: FC<()> = |ctx, props| {
+static Example: FC<()> = |ctx| {
     ctx.render(dioxus_core::prelude::LazyNodes::new(move |ctx| {
         let bump = ctx.bump();
         dioxus::builder::ElementBuilder::new(ctx, "h1")
@@ -15,3 +15,16 @@ static Example: FC<()> = |ctx, props| {
             .finish()
     }))
 };
+
+struct Props {
+    text: String,
+}
+static Example2: FC<Props> = |ctx| {
+    ctx.render(dioxus_core::prelude::LazyNodes::new(move |__ctx| {
+        let bump = __ctx.bump();
+        dioxus::builder::ElementBuilder::new(__ctx, "h1")
+            .children([{ dioxus::builder::text3(bump, format_args!("{}", ctx.text)) }])
+            // .children([{ dioxus::builder::text3(bump, format_args!("hello")) }])
+            .finish()
+    }))
+};