Update PHPUnit tests for recent changes in Drupal core

I started with a single commit: update composer.json and README.md, adding myself as a maintainer. That is enough to generate a MR and trigger the CI pipeline. I see the same failures as on #3573881.

I fixed the failing tests and some of the deprecations by replacing BlockContentType::create() with Drupal\Tests\block_content\Traits\BlockContentCreationTrait::createBlockContentType(). That method has an optional parameter to add a Body field, the equivalent of the deprecated block_content_add_body_field().

Instead of that, I could have replaced block_content_add_body_field() with Drupal\Tests\field\Traits\BodyFieldCreationTrait::createBodyField(), which is what BlockContentCreationTrait::createBlockContentType() calls. That would be one fewer levels of indirection and a few more lines of code.

Either way, in order to use non-static, protected methods of a trait, I had to remove the static declaration from LayoutBuilderRestrictionsTestBase::generateTestBlocks(). I am not sure why that method was declared static, but it does not seem to matter since it is never called statically. (That is, it is always called as $this->generateTestBlocks(), not as self::generateTestBlocks() nor static::generateTestBlocks().)

Running the test locally, I saw additional deprecation notices. I added the #[RunTestsInSeparateProcesses] attribute to each concrete test class. See the change record https://www.drupal.org/node/3548485.

I also saw this deprecation notice:

/var/www/html/core/tests/Drupal/FunctionalJavascriptTests/WebDriverTestBase.php:140
The "w3c" option for Chrome is deprecated in drupal:11.4.0 and will be forced to TRUE in drupal:12.0.0. See https://www.drupal.org/node/3460567

I fixed this by updating the configuration of my local Docker containers, following the instructions in the change record. The change record also mentions several test methods that need to be changed. I searched for these methods and did not find any uses.

The tests use the @group annotation, but that does not (yet) generate a deprecation notice. Should I replace that with the #[Group()] annotation as part of this issue?

I'm comfortable with retiring the use of the annotations here in favor of attributes. I don't think we need to keep testing for compatibility with Drupal < 10 at this point.

I am setting the status to NW for that, and assigning the issue to myself. It might be a few days before I have time for it, and I do not mind if someone else re-assigns it.

I replaced the @group annotations in tests with #[Group()] attributes. Back to NR.

Oops.

@mark_fullmer:

Done. Thanks for working with me on these issues.