Update the tested up to version for the gutenberg plugin

[talldan]

What?

Fixes #50350
Similar to #45630

Updates the 'Tested up to' version for the plugin.

I think this is usually done after a WordPress release, but must have been forgotten.

[Mamaduka]

🚢

[talldan]

I may have to use my admin powers to merge this, as the 'Pull request automation' job doesn't like the fact that I left a reference to a discussion in the PR description. 😢

Even when I update the PR description and re-run the job it still fails.

edit: it wasn't a required check, so it was ok 😌

[kgarrett67]

I was excited to see a new version of Gutenberg today, but my excitement left me when I discovered it too does not show compatibility with WordPress 6.2

[talldan]

@kgarrett67 Version 15.8 will show compatibility with 6.2. Sorry, we probably should have tried to get this into 15.7!

[youknowriad]

There's a subtlety here for the next updates that we make to this flag.

Basically this change triggers the "wordpress version" to change for the performance jobs, so we need to make sure to update the "commit hash" we use as a "comparison" basis when we do that to ensure that that "hash" is actually compatible with 6.2. The current hash is older than 6.2, so it might not be compatible and have the potential to create "wrong" numbers.

So ideally, we'd update that hash with the latests commit hash of the "wp/6.2" branch.

@oandregal mentioned to me that we could automate that commit hash and maybe automatically get the "hash" of the tag of the 6.2 version. (tested up to flag)

[oandregal]

I pushed #51381 to update to the latest commit in the wp/6.2 branch. Thought of using the wp/6.2 branch name, but it's a moving target: the branch is updated for minor releases and security updates.