add fragment cache (to match turbo cache)

[tchak]

turbo will aggressively cache pages when rendering and use the cache for history navigation. If used in combination with turbo rendering (you really should override turbo rendering with our implementation of morph), the new cache option will help.

the scenario is as follows:

• A page is rendered with the react fragment
• navigate with turbo to a new page
• turbo caches the page with the fragment containing either react rendered html or it will be empty (depending on the moment)
• navigate back by pressing the back button
• the cached page is reapplied. When coldwired tries to render the react fragment the source of the fragment is pre-rendered html or an empty string instead of JSX

This patch will preserve the fragment JSX source and try to restore it based on dom ids (they will be preserved in turbo cache)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 70320cb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR