Issue title: Allow for oEmbed fallback (using OpenGraph tags)
 Issue body: ## What problem does this address?
Currently when pasting a link that doesn't support oEmbed embedding, an error is shown, and the option to convert to a normal link is proposed

<img width="655" alt="CleanShot 2022-10-11 at 20 11 45@2x" src="https://user-images.githubusercontent.com/528287/195167899-f03fb41f-2dd0-405c-a4e3-2d56b86b46de.png">

## What is your proposed solution?
I like the way Medium handles this. It fetches the OpenGraph tags and makes a nice card. 

<img width="770" alt="CleanShot 2022-10-11 at 20 13 04@2x" src="https://user-images.githubusercontent.com/528287/195168071-57282075-ea83-4334-ae4a-a717ef0f3764.png">

Right now the embed block calls the oEmbed endpoint (`/wp-json/oembed/1.0/proxy`). It would make sense to call another API endpoint (for example `/wp-json/opengraph/1.0/proxy`) when this fails, which would return the relevant OpenGraph tags (title, description, image) needed to build the card. 

 Comments: 
 Comment 0: The core already has an API for parsing the site metadata. Currently, it's used to generate URL details popups. We can probably adopt that into an embed provider.

I started experimenting with a similar concept a few years ago - https://wordpress.org/plugins/bookmark-card/.
 Comment 1: @Mamaduka thanks for linking to your plugin. It does exactly what I'm talking about.

It would be such an improvement to the UX if we could bring something like that to core. 
{'source': 'GithubIssues', 'repo_name_with_owner': 'WordPress/gutenberg', 'issue_id': 1405057057, 'repo_stars': 8742.0}