Avoid installing multiple extensions with multiple matches

[gastaldi]

Unless it's a pattern.

Fixes #11086

[gsmet]

I thought we had tests for that? I remember we did tests some of this.

[gsmet]

@maxandersen can you check that one tomorrow morning? That's something I could include in the CR1.

[maxandersen]

@ia3andy @gastaldi I assume this code only effects if you enable new registry ?

Since default users are not affected in master where I get:

 mvn quarkus:add-extension -Dextension=jdbc
[INFO] --- quarkus-maven-plugin:1.6.1.Final:add-extension (default-cli) @ test2 ---
❌ Multiple extensions matching 'jdbc'
     * io.quarkus:quarkus-jdbc-derby
     * io.quarkus:quarkus-jdbc-mssql
     * io.quarkus:quarkus-elytron-security-jdbc
     * org.apache.camel.quarkus:camel-quarkus-jdbc
     * io.quarkus:quarkus-jdbc-mysql
     * io.quarkus:quarkus-jdbc-postgresql
     * io.quarkus:quarkus-jdbc-h2
     * io.quarkus:quarkus-jdbc-mariadb
     Be more specific e.g using the exact name or the full GAV.

[maxandersen]

This only affects new registry and looks correct thus lgtm.

[gastaldi]

Thanks, but looking at the output you pasted it seems like you're testing 1.6.1.Final.

FYI the original extension lookup algorithm was copied to the extension registry and that's what's being used in the list and add-extension commands, regardless if the Registry URL is specified or not (it falls-back to the extensions in the platform if the registry URL is not provided). This was a special case that was not caught in the existing tests but hopefully this should be good now