Social Previews: Remove i18n-calypso dependency by removing search preview header

[frontdevde]

Changes proposed in this Pull Request

• Remove Search preview header as per design in Social Previews: Remove the need for translation dependency #44489
• Remove i18n-calypso dependency
• Bump version to 1.0.2

Testing instructions

Before	After

Check if all tests pass:

• run yarn run jest -c=test/packages/jest.config.js packages/social-previews/test/index.js

Fixes #44489

[matticbot]

Test live: https://calypso.live/?branch=update/social-previews-remove-i18n-dependency

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Async-loaded Components (~25 bytes removed 📉 [gzipped])

name                                         parsed_size           gzip_size
async-load-components-web-preview-component        -97 B  (-0.0%)      -25 B  (-0.0%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[getdave]

Thanks for tackling this and taking on the NPM version bump.

I tried testing this by checking out the PR and booting Calypso. I then went to the "Preview" modal in a post and looked at the Google Search result. Unfortunately I saw this even after refreshing and trying again a few times.

I think this is because these fixes are made in the package not in the Calypso components. That is correct because until this PR is merged then we are still using the old components in Calypso.

To avoid this problem and make this PR easier to test could we first ship the PR to get WP.com Calypso to use the NPM package components? Then we can easily test this PR.

[frontdevde]

I think this is because these fixes are made in the package not in the Calypso components.

Yes, these changes are intentionally only applied to the social-previews package as other products incl. Calypso will consume this package going forward. And yes, I don't mind shipping #44604 first. :)

[getdave]

Now that WP.com modal is consuming the NPM package's components I've gone ahead and rebased the branch and everything is looking as it should.

I'd say we're good to 🚢 and publish the new version to NPM.

[getdave]

Thanks for spotting this!