Implement robust hydration warning system

[brainkim]

Crank currently implements hydration but lacks a robust hydration warning system, which is present in frameworks like React. Hydration warnings are important for detecting mismatches between server-rendered and client-rendered DOM, helping developers debug hydration issues and ensuring consistent user experiences.

Feature requirements:

• Add a warning system to detect hydration mismatches between server and client renders.
• Emit clear, actionable warnings in the console when mismatches occur.
• Provide documentation or examples for interpreting and troubleshooting hydration warnings.
• (Optional) Allow configuration to enable/disable or adjust the verbosity of warnings.
• Implement a suppressHydrationWarnings attribute (similar to React) to allow developers to intentionally suppress hydration warnings on specific elements when mismatches are expected or acceptable.

This feature would improve developer experience and bring Crank more in line with established best practices in JavaScript frameworks.

[brainkim]

As discussed in #292, I’m exploring a unified meta-prop API pattern (boolean/string values) that could cleanly support warning suppression for hydration, similar to how we're handling selective re-rendering via the copy prop. I’m loathe to implement React’s suppressHydrationWarning, since the API feels verbose and short-sighted.

Proposal:

Similar to the proposed copy prop extensions, allow a special hydration prop to accept:

• hydration={true} (hydrate and warn)
• hydration={false} (suppress all hydration warnings recursively)
• hydration="class children" (only hydrate children, class, suppress other warnings)
• hydration="!children (hydrate all props besides children)

Additionally, I’m considering allowing the hydration prop to accept DOM nodes.

• hydration={node} start hydration with this node at this element.

For 0.7, I’m planning to ship the boolean/string API.