Switch to Fragment short syntax (from <Fragment> to <>)

[Aljullu]

There has been some discussion in a couple of PRs in parallel whether we should use <Fragment> or <>:

• Add Shipping settings to Cart block #1561 (comment)
• Implement __experimentalCreateInterpolateElement for translations. #1736 (comment)

This issue is to centralize the discussion and, in case we agree to switch from <Fragment> to <>, enable the appropriate ESLint rule.

Some things to notice:

• We have been consistently using <Fragment> until now.
• Gutenberg is inconsistent about this and uses both, <Fragment> and <>.
• Using <Fragment> means we need to import it. Considering we currently have three different packages where it can be imported from (@wordpress/element, wordpress-element and react), that might be a source of unexpected bugs that could be prevented if we used the short syntax.
• Fragments in React docs

[nerrad]

cc @woocommerce/wc-admin - this is a code style/standard change that we should decide on together so we keep the projects align. For the next cooldown period it'd be good to create an eslint package (extending WP linting package) that standardizes around code styles/standards for the project and then we can just submit pulls to that package.

[mikejolley]

Been using <> in new PRs since learning about it. The convenience of that is a massive ➕ .