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/recoil/examples/selectors.rs

@@ -5,7 +5,7 @@ const A: Atom<i32> = |_| 0;
 const B: Atom<i32> = |_| 0;
 const C: Selector<i32> = |api| api.get(&A) + api.get(&B);
 
-static App: FC<()> = |ctx, _| {
+static App: FC<()> = |ctx| {
     use_init_recoil_root(ctx, |_| {});
     rsx! { in ctx,
         div {
@@ -16,12 +16,12 @@ static App: FC<()> = |ctx, _| {
     }
 };
 
-static Banner: FC<()> = |ctx, _| {
+static Banner: FC<()> = |ctx| {
     let count = use_read(ctx, &C);
     ctx.render(rsx! { h1 { "Count: {count}" } })
 };
 
-static BtnA: FC<()> = |ctx, _| {
+static BtnA: FC<()> = |ctx| {
     let (a, set) = use_read_write(ctx, &A);
     rsx! { in ctx,
         div { "a"
@@ -31,7 +31,7 @@ static BtnA: FC<()> = |ctx, _| {
     }
 };
 
-static BtnB: FC<()> = |ctx, _| {
+static BtnB: FC<()> = |ctx| {
     let (b, set) = use_read_write(ctx, &B);
     rsx! { in ctx,
         div { "b"