Implement __experimentalCreateInterpolateElement for translations.

[mikejolley]

Following on from #1043, this PR implements the new __experimentalCreateInterpolateElement from the wordpress/element package. It allows us to dynamically insert HTML (in this case anchors) into a translatable string.

For translators, instead of:

Product rating is disabled in your %sstore settings%s.

They will be able to translate a more obvious:

Product rating is disabled in your <a>store settings</a>.

And the link will be inserted. It also means we can avoid using RawHTML and escapeHTML to show string based HTML content.

Since __experimentalCreateInterpolateElement is not available in WordPress yet, only Gutenberg master, this pulls in the package via package.json.

[nerrad]

Looks good to me Mike. I do have a comment about some attributes added to the links but I'll leave it up to you what direction you go and will pre-approve this. Something to keep in mind is that it looks like we're going to remove the experimental prefix on this function at some point in the near future.

However, it doesn't really impact this work because it's pinned to a version (we can just update when needed).

Also, I confirmed by comparing a build on master with a build on this branch that the bundle-sizes don't really change at all, so that's good!

Let's

[nerrad]

Why do we use both noopener and noreferrer here (and in other places in this pull), could we just use noreferrer?

[mikejolley]

I misread the linting rule and thought both were required. Referer could be useful (?) so Ill use noopener.

[mikejolley]

hmm actually the rule does enforce both. eslint(react/jsx-no-target-blank) You cannot just use one or the other...

[nerrad]

🤔 Interesting, from this it appears this targets both because of older browser support (but in this context we probably want noreferrer anyways). I can't think of any reason offhand why doing both creates a problem, so let's just keep it as is for now.

[nerrad]

Looks like there's an issue that got started around this rule enforcing both :)

[Aljullu]

For reference: a similar discussion happened in Storefront repo. In the end we ended up using rel="noreferrer". We don't have this ESLint rule so it was possible to use only one in that case.

[mikejolley]

Thanks for the links. I think we're okay using both to keep eslint happy until that issue is fixed. There doesn't appear to be consequences in doing so.