Improve hook_help() to explain the actual Composer requirements

I think I'm happy enough with this.

Beautiful! 🤩

Actually, there's one thing missing: we need to update \Drupal\package_manager\Validator\ComposerValidator::validate() accordingly?

I thought about that...but I didn't see any real need. The error messages that come back from the validator explain everything that the updated hook_help does, with the same links to Composer's documentation. What sort of changes were you imagining?

I was just thinking that now it's inconsistent: one kind of problem provides no detailed explanation and points you to hook_help(), the other does not.

But you're right that the message in HEAD that points one to hook_help() is much more complicated to explain, which justifies that link. That same justification is less possible here.

It could be as simple as adding See <a href=":package-manager-help">the help page</a> for information on how to configure Composer to download packages securely. I don't think that'd be harmful? Because the help page does actually give you the Composer commands directly!

So: RTBC, and I'll let you decide whether it's worth being consistent or not.

Decided to go for consistency. It's helpful, I think, to link to the actual commands where possible.

I am reviewing but assigning to @phenaproxima to fix the unknown word issue.

Still needs a follow-up. And coding standards checks are failing.

Looks good, just a couple small suggestions

Linking the issue @phenaproxima created to fix the pre-existing bug @tedbow spotted in reviews.

Follow-up was created, nits addressed, tests are present. This is ready!

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