feat: add support for client only lazy loading with dynamic

[Valerioageno]

Context & Description

Closes: #258

This PR extends the usage of the dynamic function, making its usage the same as Next.js

Quick takeaways:

1. The tuono-lazy-fn-vite-plugin gets completely dropped
2. dynamic takes an obj as second argument { ssr: boolean, loading: JSX.Element }
3. The whole implementation is heavily inspired by the Next.js implementation

Good to know:
using ssr: true we get the following console error

This is expected because what is rendered on the server doesn't match the client.

After investigating how Next.js fixed this issue, I found that they have an error boundary that enhances and filters the console errors triggered by React. Basically, every dynamic hydration error gets labeled by next/dynamic so they automatically remove it at runtime!

I'd propose to address the ErrorBoundary after this and release the dynamic with the console error (which is fine since it is not blocking for the users)

[marcalexiei]

Few additional considerations:

• It would be useful to add some unit tests about this component for both client and ssr case (we should be able to mock window via vitest).

• About

  release the dynamic with the console error (which is fine since it is not blocking for the users)

  We should add the documentation about dynamic() usage alongside a warning about the expected error (informing that it will be fixed in the next release)

• Maybe this could be also added to the tutorial but I think is better to do it after we fixed the ssr error