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

@@ -1,7 +1,7 @@
 use dioxus_core::component::fc_to_builder;
 use dioxus_core::prelude::*;
 
-static BLAH: FC<()> = |ctx, _props| {
+static BLAH: FC<()> = |ctx| {
     let g = "asd".to_string();
     ctx.render(rsx! {
         div {
@@ -17,7 +17,7 @@ pub struct ExampleProps {
     some_field: String,
 }
 
-static SomeComponent: FC<ExampleProps> = |ctx, _props| {
+static SomeComponent: FC<ExampleProps> = |ctx| {
     let blah = rsx! {
         div {}
     };