Fix recipe IDs in applied recipes state

I thought about this a bit and I realized we probably don't even need to read composer.json if we stop using the event subscriber and just add the "mark as applied" stuff as a normal batch operation. Opened !7 to propose this. What do you think - will that work? I like it most of all because it keeps everything in the Hooks class and minimizes the amount of code that a generated profile will have.

Gave this a quick manual test in the context of Drupal CMS and confirmed that it works as expected (the state key contained the names of the recipes I selected at the beginning of the process).

Merged !7 into 1.x.

I would have preferred the event subscriber because it works no matter how recipes are applied, but I can make this work.

Automatically closed - issue fixed for 2 weeks with no activity.