[far backport] drupal_cms_starter should allow Automatic Updates 4, to facilitate going to Drupal 11.2

Should this be specifying a version at all?

Tests are failing due to a known flaw in Recipe Installer Kit. I don't feel like fighting it right now, certainly not this close to the release of Drupal 11.2 and a certain chance of us blocking early adopters of Drupal CMS from updating core.

I'm merging it.

@catch, there is no need to specify a version; Automatic Updates 4.x is only at 4.0.0-alpha2 (and will need to be tagged stable before Drupal core 11.2 is released, since project templates have minimum-stability: stable, and AU 4.x is identical to 3.1.x anyway -- which is stable -- apart from the internal integration with core's Package Manager).

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