Composer install fails on Drupal 11 and Drupal CMS

I updated the composer.json to add the Drupal 11 core dependency.

I was able to test this using the fork by adding the alerts fork as a repository to my local root composer.json file:

    "repositories": {
        "alerts": {
            "type": "package",
            "package": {
                "name": "drupal/alerts",
                "version": "2.0.x-dev",
                "type": "drupal-recipe",
                "source": {
                    "url": "https://git.drupalcode.org/issue/alerts-3502960.git",
                    "type": "git",
                    "reference": "ea7d736f1ffa995bc29dcdf975e92db20cf8498b"
                }
            }
        },
        "drupal": {
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        }
    },

Running ddev composer require 'drupal/alerts:2.0.x-dev' did not produce any errors and produced the following results instead:

./composer.json has been updated
Running composer update drupal/alerts
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals
  - Locking drupal/alerts (2.0.x-dev ea7d736)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 0 updates, 0 removals
  - Syncing drupal/alerts (2.0.x-dev ea7d736) into cache
  - Installing drupal/alerts (2.0.x-dev ea7d736): Cloning ea7d736f1f from cache
Generating optimized autoload files
59 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.

This solved the issue of not being able to install the recipe via composer.