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

@@ -14,10 +14,28 @@ struct SomeProps {
     name: String,
 }
 
-static Example: FC<SomeProps> = |ctx, _props| {
+static Example: FC<SomeProps> = |ctx| {
     ctx.render(html! {
         <div>
             <h1> "hello world!" </h1>
         </div>
     })
 };
+
+// #[test]
+#[derive(PartialEq, Clone)]
+struct MyStruct {
+    a: String,
+}
+
+fn check_before_to_owned() {
+    let new_str = MyStruct {
+        a: "asd".to_string(),
+    };
+
+    let out = town(&new_str);
+}
+
+fn town<T: ToOwned + PartialEq>(t: &T) -> T::Owned {
+    t.to_owned()
+}