ComposerSettingsValidator should run `composer config` to determine if HTTPS is enabled

@tedbow @TravisCarden On November 14, this was assigned to Travis for <4 hours. Without context as to why it was assigned to him, nor why it was unassigned. Can we please get clarity on this? 🙏

#11 not sure why now 😔

There are no MR comments awaiting replies from @TravisCarden. He made some suggestions on the issue but I think others could implement this.

#12: k, thanks!

I think this qualifies as a security improvement because it makes it less likely that PM/AU will reach the wrong conclusion if composer's configuration structure changes in the future: composer config secure-http SHOULD provide BC.

We need a test on ComposerInspector at least. I haven't checked further

Not blocking on #3320792: Make build tests fail 1) more explicitly, 2) earlier when possible (failing StatusCheckEvent subscribers) but I have brought in a change from there because it makes debugging build tests easier.

Going to stop working on this so I can get some of the other child issues of #3316368: Remove our runtime dependency on composer/composer: remove ComposerUtility

Anyone else can review my work and try to get these tests passing

I still trying to get the test to pass

Tests are passing. I brought in some changes from 3320792-build-status-report that need to be removed. Also add a couple other comments on the MR

12 remarks in MR, ~50% of which are nits. But there definitely are more tests to be written still! 😊

Almost there!

Needs work for a bit of missing test coverage plus a formatting nit.

I left two questions on the merge request for @tedbow that you don't have to address, @yash.rode.

For some reason your boo-far made me laugh out loud 🤣👍

RTBC — with two questions for @tedbow 😊

Because of #3337697: Custom commands fail for 7.4 I am going to run tests on 9.5 without code checks assuming if code checks are ok on 10.1 they are will be ok on 9.5. Also we aren't merging into 9.5 core

🎉