fix: URL and JSONbin storage

[LiamMartens]

Updated URL storage provider to support themes and metadata
Updated JSONbin to support metadata

Fixes #1164

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
figma-tokens	✅ Ready (Inspect)	Visit Preview	Aug 22, 2022 at 3:45PM (UTC)
ft-storybook	✅ Ready (Inspect)	Visit Preview	Aug 22, 2022 at 3:45PM (UTC)

[LiamMartens]

@six7 I did notice JSONBin currently always asks to recover local changes (also in the live plugin), We may want to review this behavior - but it's a bit of a weird one because it's the only provider type we automatically sync as opposed to the git providers. Perhaps there is merit in just aligning the logic altogether and also making this a manual action like the git providers?

[github-actions]

Commit SHA:9b334495ac6b8ccd6ae47464831de0a3da3717ff

Test coverage results 🧪

Code coverage diff between base branch:next and head branch: fix/url-storage-and-jsonbin-metadata-and-themes 

Status	File	% Stmts	% Branch	% Funcs	% Lines
🟢	total	67.64 (0.34)	58.95 (0.41)	64.08 (0.17)	67.82 (0.35)
🟢	src/app/store/providers/jsonbin.tsx	72.22 (17.93)	74.36 (25.79)	83.33 (16.66)	72.86 (18.45)
🟢	src/storage/JSONBinTokenStorage.ts	100 (0)	82.14 (0.89)	100 (0)	100 (0)
🟢	src/storage/RemoteTokenStorage.ts	95.45 (9.09)	78.57 (14.28)	100 (0)	95.45 (9.09)
🟢	src/storage/UrlTokenStorage.ts	100 (14.29)	78.57 (8.57)	100 (20)	100 (14.29)
✨ 🆕	src/utils/date/compareUpdatedAt.ts	71.43	50	100	71.43

[github-actions]

Commit SHA:25725d216579665ce8788c8478dbd4618903ba2a
Current PR reduces the test coverage percentage by 1 for some tests

[six7]

Two version and updatedAt placements

We now have 2 places where we track updatedAt and version, is this intended? I really like placing it in metadata fwiw!

Other than that this works as intended 🙏 Would love to know the thoughts behind the two version and updatedAt placements

[six7]

@six7 I did notice JSONBin currently always asks to recover local changes (also in the live plugin), We may want to review this behavior - but it's a bit of a weird one because it's the only provider type we automatically sync as opposed to the git providers. Perhaps there is merit in just aligning the logic altogether and also making this a manual action like the git providers?

Yeah agree, we should align as much as we can, making this a manual pull/push action would be great. I'll create an issue

[LiamMartens]

@six7 I updated the PR to move the version and updatedAt keys to the metadata and remove them from the root object. The root object keys are still supported when reading.