HTML API: Update code style so it passes when backported into Gutenberg

[dmsnell]

​GitHub PR#4360

During the attempted merge of WordPress/gutenberg#49966 the PHP linting rule rejected the PR, even though it's a direct copy from Core.

In this PR we're adding spacing so that we can merge the "blessed" PR without creating conflicts between the two repositories.

Somehow our linting rules aren't aligned and it would be good to fix that, but in order to focus on scope I'd like to get this change in to unblock the backport.

This patch only introduces new whitespace and should not impact code in any way.

Trac ticket #58170-trac

During the attempted merge of WordPress/gutenberg#49966 the PHP linting rule rejected the PR, even though it's a direct copy from Core.

In this PR we're adding spacing so that we can merge the "blessed" PR without creating conflicts between the two repositories.

[zieladam]

In 55674:

HTML API: Update code style so it passes when backported into Gutenberg.

This changes the indentation of a variable in class-wp-html-tag-processor.php
to satisfy both WordPress and Gutenberg linters.

Props dmsnell, ntsekouras.
Fixes #58170.

@hellofromtonya this apparently was fine in Core but in Gutenberg it was rejected. I'm not sure why or what happened, as the line in question was called out in review as a surprise that Core's linting didn't catch it. To the best of my recollection I made this change and submitted it only to find the Core linting rejected it, but maybe I messed up when I did that check, because it passes now.

Somewhere in here our linters don't agree, and I figured you might be the person to notify about it.

Committed in r55674 / ​https://github.com/WordPress/wordpress-develop/commit/fea66becf567d3cdcaa40d6edbec6e0d20df362e

I wonder how the previous version of that file (before your patch) could possibly pass the Core CI checks? When I test this in my local environment, I get linter errors.

sounds like a good question @anton-vlasenko 🤷‍♂️

@anton-vlasenko @dmsnell The linter throws a warning rather than an error.

In WP-Dev, I believe the tests directory action fails on both warnings and errors, but the src directory only fails on errors. I guess the GB repo fails for both warnings and errors too.

[SergeyBiryukov]

#58530 was marked as a duplicate.