[MNG-7841] Insecure mirrors are only whitelisted when defined in global settings

**[Delany](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=delany)** opened **[MNG-7841](https://issues.apache.org/jira/browse/MNG-7841?redirect=false)** and commented

The second option to fix a blocked repository at https://maven.apache.org/docs/3.8.1/release-notes.html#how-to-fix-when-i-get-a-http-repository-blocked, i.e. "keep the dependency version but [define a mirror in your settings](https://maven.apache.org/guides/mini/guide-mirror-settings.html)." only works when the settings are global (--global-settings). An insecure repository defined in the user settings (–settings) will still be blocked.

---

**Affects:** 3.9.3

Reproduce the blocked insecure repository case using a mirror in user settings with --settings, then compare it with the working --global-settings path described in the issue. Done means an insecure repository mirror defined in user settings is whitelisted and no longer blocked, while the existing global-settings behavior remains intact.

Written by the indexing model from the issue text.