[MRESOLVER-495] Provide AuthenticationSelector based on host/realm instead of repository id

**[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)** opened **[MRESOLVER-495](https://issues.apache.org/jira/browse/MRESOLVER-495?redirect=false)** and commented

Currently the [`DefaultAuthenticationSelector`](https://github.com/apache/maven-resolver/blob/master/maven-resolver-util/src/main/java/org/eclipse/aether/util/repository/DefaultAuthenticationSelector.java#L56) only returns authentication info based on the repository id. In order to reuse the same authentication for multiple repositories (on the same or even on different servers) it should be possible to add authentication for a host (and potentially port/realm/scheme).

Apache HttpClient uses the `AuthScope` class (https://hc.apache.org/httpcomponents-client-4.5.x/current/httpclient/apidocs/org/apache/http/auth/AuthScope.html) to bind credentials to requests.

Compare with https://datatracker.ietf.org/doc/html/rfc7235#section-2.2.

---

**Issue Links:**
- [MNG-6895](https://issues.apache.org/jira/browse/MNG-6895) Add aliasing feature for settings.xml:///servers/server

- [MNG-5585](https://issues.apache.org/jira/browse/MNG-5585) match server credentials based on server realm

Start with maven-resolver-util/src/main/java/org/eclipse/aether/util/repository/DefaultAuthenticationSelector.java and review how authentication is currently selected by repository id. Compare the desired matching scope with Apache HttpClient's AuthScope and RFC 7235 section 2.2. Done should allow authentication reuse across repositories using host and potentially port, realm, and scheme while preserving the existing selection behavior.

Written by the indexing model from the issue text.