Ensure that only one process can be applying a recipe at a time

Seems like a perfect use case for the lock service.

But can the drupal script access that? 🤔

If it fully bootstraps Drupal, which AFAIK it does, then it should be able to access all services.

I think we should address this in phase 2.

robert-arias → made their first commit to this issue’s fork.

Added locking mechanism in recipe command execution, and tests.

Locks are very tricky when something is batched. Look at the ConfigImporter ... it uses the persistent lock service. We're going to need to do the same.