Set a config checkpoint before applying a recipe

+1 to this.

Working on it.

I have added the code to add configuration checkpoint when an recipe is activated via project browser,
Please review.

Address review things.

This seems quite straightforward to me, but it needs a test. RecipeActivatorTest already exists and it should be pretty simple to add a couple of assertions that a config checkpoint was created when a recipe was applied.

I addressed the MR feedback and added test assertions for the checkpoints.

I have updated the MR with some pipeline fixes, still some Functional Javascript task is failing.
Moving it to Needs Work.

This should be backported to 2.0.x because checkpoints have existed since Drupal 10.3 (they were added with the rest of the recipe system), so there's no reason not to do that.

tim.plunkett → made their first commit to this issue’s fork.

Thanks, gang!

merged on 2.1.x and cherry-picked clean to 2.0.x