Fix SEO > LDJson Hydration warning

[cartogram]

When I moved this library to use React.createElement from plain jsx tags, I failed to remember that the script tag data needs to be passed in "dangerously" 💀 ... without this, the data is serialized and causes a mis-match on server/client.

Thanks @wizardlyhel for pointing this out.

Before

After

[github-actions]

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset.
If the changes are user-facing and should cause a version bump, run npm run changeset add to track your changes and include them in the next release CHANGELOG.
If you are making simple updates to examples or documentation, you do not need to add a changeset.

[frehner]

Could it also be JSON.stringify() instead? Just wondering.

[cartogram]

It is already by stringified because it comes from the generateSeoTags as a string.

[cartogram]

We could move that stringification here (put in on the user). Perhaps something to revisit when we see more usage.

[wizardlyhel]

could be possible? set on text with JSON.stringify and we won't get appsec warning us about using dangerouslySetInnerHTML