Fix failing "updated deps" test-runs by upping mglaman/phpstan-drupal to latest

Problem/Motivation

With the 1.1.26 release of mglaman/phpstan-drupal, we see our "updated deps" test-runs fail on both 10.0.x and 10.1.x

----- Original Problem/Motivation -----
We upped the removal-drupal-version from 10.0.0 to 11.0.0 for the deprecated constant REQUEST_TIME in #3318985: Bump REQUEST_TIME deprecation to Drupal 11 → .

Our core/phpstan-baseline.neon still suppresses based on 10.0.0. No problem.
Until a combo of the newest phpstan/* and/or mglaman/phpstan-drupal-packages decided around Dec. 23 that they had enough.
Our "updated deps" testruns on 10.0.x and 10.1.x starting failing with a flood of unmatched error patterns.

Steps to reproduce

https://www.drupal.org/node/3060/qa →

Proposed resolution

I think here we can only bump mglaman/phpstan-drupal to latest (including upping the version constraint in composer.json) AND refresh the baseline at the same time.

(c) @mondrake

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet