Fix phpstan errors

I would recommend holding off on all of these pipeline fixes until the D11 branch is merged. Otherwise we're going to have major conflicts which will be very hard to manage.

Many of these are needed for D11 compatibility. The D11 issue is being split into focussed issues. This issue could be part of that process.

@liam morland legitmate issues, sure, but making phpstan green in CI is not required for D11. The branch also needs a rebase with HEAD.

D11 branch is merged.

The phpstan pipeline is now fixed, but one test is now failing. Oddly enough it doesn't fail on my local machine.

Tests are passing again on 6.3.x. Please reroll and get tests to pass.

Tests are passing again on 6.3.x. Please reroll and get tests to pass.

BTW, it fine to ignore a few tricky phpstan errors via // @phpstan-ignore-next-line property.notFound.

@see https://phpstan.org/user-guide/ignoring-errors

BTW, it fine to ignore a few tricky phpstan errors via // @phpstan-ignore-next-line property.notFound.

@see https://phpstan.org/user-guide/ignoring-errors

There is no phpstan error. Please review.

See #9

The failing test is only happening in D11.1

Fixed the last test failure.

I am going to go with this MR is good enough. The only breaking change is the removal of the completely unused \Drupal\webform\Plugin\WebformElement\TextFormat::hasCompositeElement added in 2017.

Automatically closed - issue fixed for 2 weeks with no activity.