Composer failure after ai_search moved out from ai

Problem/Motivation

composer update --lock
  Problem 1
    - Root composer.json requires drupal/ai_search == 1.1.4.0 (exact version match), found drupal/ai_search[1.1.4] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

Root cause: TL;DR Drupal Packaglist magic.

Even if the module's composer.json does not depend on drupal/ai_search but ai:ai_search is listed in its info.yml as dependency therefore Drupal Packagist automatically adds a dependency on drupal/ai_search metapackage. See proof in a project's composer.lock:

        {
            "name": "drupal/ai_vdb_provider_milvus",
            "version": "1.1.0-beta2",
            "source": {
                "type": "git",
                "url": "https://git.drupalcode.org/project/ai_vdb_provider_milvus.git",
                "reference": "1.1.0-beta2"
            },
            "dist": {
                "type": "zip",
                "url": "https://ftp.drupal.org/files/projects/ai_vdb_provider_milvus-1.1.0-beta2.zip",
                "reference": "1.1.0-beta2",
                "shasum": "11859c5c7a2ede228a38a8050478b8cdf09dbe67"
            },
            "require": {
                "drupal/ai": "^1.1.0",
                "drupal/ai_search": "*",
                "drupal/core": "^10.2 || ^11",
                "drupal/key": "^1.18"
            },
            "require-dev": {
                "drupal/search_api": "^1.35"
            },

Steps to reproduce

Run composer update --lock on a project where a 1.1.x version of this module is installed.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes