GitExcluder should use ComposerInspector instead of ComposerUtility

@Wim Leers sorry I didn't realize a problem with the idea until I saw it done

The functional tests that failed here https://www.drupal.org/pift-ci-job/2611778 → pass for me locally. Will wait to investigate until the next test run comes back

@tedbow explained the rationale for his changes to me over Zoom. Although I'd like Wim's +1 before we commit this, I'll RTBC once Ted makes the changes I've asked for, especially the one about where we throw the LogicException.

I like Ted's approach of making sure we present the user with the problem that caused CollectIgnoredPathsEvent to fail. That keeps things transparent and debuggable, and means we don't have to write a whole other validator. What's not to like?

I think this is good.

RTBC assuming tests pass, and assigning to Wim for final sign-off on what we did here, and (if he feels like it) commit.

Did a thorough final review before merging (only spotted 2 tiny nits: one comment, one strict types declaration), merged in upstream … all green so: 🚢

This unblocked 📌 UnknownPathExcluder should use ComposerInspector instead of ComposerUtility Fixed .

Follow-up created for pre-existing problem I spotted during my final review: 📌 Regression in #3343827: GitExcluderTest should test with composer/installers enabled Fixed .

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