Unpack composer plugin impact

The problem is that it removes the recipe from Composer.json.

It is supposed to do this. That's the point of unpacking. You unpack so that the recipe is no longer part of the Composer-managed dependency tree. :)

I think what we'll need to do here is adjust the recipe finder so that it simply scans composer.json to find out where recipes would be installed, and look there.

Re-targeting for 2.1.x; I'm not sure this will need to be backported.

Let's backport this to 2.0.x. The "read composer.json" way should still work on Drupal 11.1 and older, and honestly it's probably more reliable (in certain edge cases) than the old way.

This is a duplicate of 🐛 RecipeActivator needs to handle unpacked recipes that aren't Composer-managed Active , which is a bit further along and more robust.