URL Details: Update regex to include og:description

[Mamaduka]

Description

PR updates regex to include og:description when looking for valid site descriptions.

Fixes #33754.

P.S. Sorry about whitespace changes. Let me know if you want me to revert it.

How has this been tested?

Unit tests are passing.

Types of changes

Enhancement

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR (please manually search all *.native.js files for terms that need renaming or removal).

[hellofromtonya]

The og:description regex and associated test data are ready to go. Well done @Mamaduka 🥇 I'm approving this PR for the og:description enhancement.

But I'd suggest reverting the whitespace removal changes to maintain an og:description enhancement atomic commit. Why? Code churn. The whitespace changes do not impact test results, code quality, or the goals of the og:description enhancement.

Thanks @Mamaduka 🙌

[TimothyBJacobs]

If I'm reading this right, it seems like whether og:description or description is picked is solely based on what comes first in the document. Should we be more intentional and query one of them first?

[getdave]

If I'm reading this right, it seems like whether og:description or description is picked is solely based on what comes first in the document. Should we be more intentional and query one of them first?

Is there any existing pattern in place for preferring og: or otherwise?

IMHO it would seem reasonable to prefer OG and fallback to other options.

[Mamaduka]

@TimothyBJacobs is right.

Value is picked based on what comes first in the document. It is similar to how we get image URLs.

I don't have a strong preference here.

[Mamaduka]

@hellofromtonya, thanks for the review.

I was about to revert trailing whitespace changes, but it looks like settings is set in the project on the .editorconfig level:

gutenberg/.editorconfig

Line 13 in d209b27

trim_trailing_whitespace = true

Reverting changes will mean that we'll get similar unwanted changes tracked in the future.

[getdave]

@Mamaduka If this matches the existing pattern for returning whatever comes first in the document then I'm happy to roll with that.

Nice work here. I'll let others feedback on whitespace as I also have this question in another PR.

[Mamaduka]

Thanks, everyone, for the reviews. I'm going to merge this since trailing whitespace changes matches the editor configuration.