UnknownPathExcluder should use ComposerInspector instead of ComposerUtility

@tedbow's feedback is addressed, which removes the need for issue summary updates and a follow-up.

I:

• implemented composer config --file, as discussed during yesterday's meeting
• proved to @tedbow that we're tightly complying with composer.lock validation by tightening that validation — even though that's arguably out of scope. I figured since the question was surfaced here, it was worth tightening here. I'm fine with splitting it off to a separate issue though.

Deferring the strict lock checking to 📌 Explicitly validate lock files everywhere: `composer validate --check-lock` Fixed .

One pointed question, one potential small refactor...

🏓

This looks good to me

Sorry, still not grokking something. I will hop in a Zoom or something to clear it up...

Per https://git.drupalcode.org/project/automatic_updates/-/merge_requests/75..., I think this should be postponed on 📌 GitExcluder should use ComposerInspector instead of ComposerUtility Fixed to avoid having the same discussion in two places.

📌 GitExcluder should use ComposerInspector instead of ComposerUtility Fixed landed.

IMO this is now ready — curious to hear what @phenaproxima thinks!

Discussed with Wim and I think this is mostly really good. I approve of the added explicitness in calling ComposerInspector::validate().

There are a couple of things we should streamline, though, for clarity. Self-assigning to handle those.

Changes look good, 🚢 (but first fix the failures due to expectations needing updates)

Assigning to Wim for final review and commit.

Marked #3344583 as NW as very helpfully suggested by @phenaproxima: #3344583-19: ComposerInspector::validate() should throw ComposerNotReadyException instead of \Exception → 😊

📌 Explicitly validate lock files everywhere: `composer validate --check-lock` Fixed is now less postponed: #3346520-4: [PP-1] Explicitly validate lock files everywhere: `composer validate --check-lock` → .

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