Inconsistent extension module machine name (doubled for composer)

The behavior of the Composer namespace assignment is by design to prevent collisions. Composer namespaces do not necessarily match project names. Is manual correction needed in this case?

Well, manual correction would be better for sure. I don't understand why there would be a name collision in my case. Did I missed something? :-S
Thanks for your time! :)

Facing the same issue with https://www.drupal.org/project/webtheme_default_content/releases/10.0.x-dev →

composer require 'drupal/webtheme_default_content-webtheme_default_content:10.0.x-dev@dev'

I facing the same issue with:
https://www.drupal.org/project/gleap →

composer require 'drupal/gleap-gleap:^1.0'

Facing the same issue with
https://www.drupal.org/project/ui_patterns_field_group/releases/2.0.x-dev →

composer require 'drupal/ui_patterns_field_group-ui_patterns_field_group:2.0.x-dev@dev'

It appears that a manual correction is required to assign the composer namespace.

Perhaps a new composer parser plugin could be developed to identify departed sub-modules in the `.info.yml` file.
Or to declare sub-modules or sub-themes.

Here's an example:

sub_modules:
  - ui_patterns_field_group

sub_themes:
  - subtheme

departed_sub_modules:
  - ui_patterns: ui_patterns_field_group
  - ui_patterns: ui_patterns_ds
  - ui_patterns: ui_patterns_library

departed_sub_themes:
  - bootstrap_barrio: subtheme

I suggest the following:

• Initially switch to the default https://packagist.org or https://repo.packagist.org behavior
• Follow the listed info schema specified in the .info.yml
• Handle current sub-modules or sub-themes
• Handle departed sub-modules or sub-themes
• Integrate a composer plugin for departed extensions

Implementing these measures may assist maintainers in resolving the issue themselves.
I have noticed that some modules like ui_patterns having issues on every departed sub module.

Would changing the logic to prevent collisions be helpful?

What is next for this issue?
Drop using the modules, or use the parent module version, with the sub module?