Parse composer.json for the project name for update module

A followup issue from the great git migration got marked outdated recently, which, fair enough. The remaining scope of it was that dev versions od modules deployed with git deploy and then composer did't work with update.php. This looked like the modern home of that although this seems to only about naming, rather htan version numbers, abd to be yet another duplicate in a chain?

Is there an infra issue for #38?

My clever retitle of one of the related issues is a little misleading about just what old technical debt this is, and that the issue has survived not only multiple deployment best practices but also multiple d.do packaging systems and even core version control systems. 🤫

Removing circular issue references.

And, if I'm reading the issue right and the scope was reduced, does that mean this was reduced to the project name only, and not supporting the version number problem?

https://packagist.org/packages/drupal-composer/info-rewrite seems to support only Composer 1 and 2.

✨ Add tracking for when recipes from Drupal.org are applied Active might have this implemented in ComposerHelper::getPackageName(), not hooked up to update module yet.