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

@@ -11,7 +11,7 @@ fn main() {
 }
 
 // this is a component
-static Example: FC<()> = |ctx, _props| {
+static Example: FC<()> = |ctx| {
     let (event, set_event) = use_state(&ctx, || None);
 
     let handler = move |evt: MouseEvent| {
@@ -48,10 +48,10 @@ struct ExampleProps {
     name: String
 }
 
-static Example2: FC<ExampleProps> = |ctx, props| {
+static Example2: FC<ExampleProps> = |ctx| {
     ctx.render(rsx!{
         div {
-            h1 {"hello {props.name}"}
+            h1 {"hello {ctx.name}"}
         }
     })
 };