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.

examples/website.rs

@@ -19,7 +19,7 @@ mod state {
     }
 }
 
-static APP: FC<()> = |ctx, props| {
+static APP: FC<()> = |ctx| {
     ctx.render(html! {
         <div>
 
@@ -28,7 +28,7 @@ static APP: FC<()> = |ctx, props| {
 };
 
 /// Draw the navbar on top of the screen
-static Navbar: FC<state::Route> = |ctx, props| {
+static Navbar: FC<state::Route> = |ctx| {
     ctx.render(html! {
         <div>
 
@@ -36,7 +36,7 @@ static Navbar: FC<state::Route> = |ctx, props| {
     })
 };
 
-static Homepage: FC<()> = |ctx, props| {
+static Homepage: FC<()> = |ctx| {
     ctx.render(html! {
         <div>