Allow extension to define CLI plugins with aliases

[iocanel]

Currently, when an extension defines a plugin, the name is inferred by the artifact id. In some cases that can be annoying and this pull request addresses that, by optionally allowing user to specify the alias they need.

[iocanel]

cc @metacosm AFAIR, this is something that you mentioned that you'd like to have.

[metacosm]

Indeed, that would be useful. Thank you!

[geoand]

@iocanel this needs a formatting fix

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 95f1c0b.

Failing Jobs

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✔️	JVM Tests - JDK 17			Logs	Raw logs	🔍
✔️	JVM Tests - JDK 21			Logs	Raw logs	🔍
✖	JVM Tests - JDK 17 Windows	Build	Failures	Logs	Raw logs	🔍

Full information is available in the Build summary check run.
You can consult the Develocity build scans.

Failures

⚙️ JVM Tests - JDK 17 Windows #

- Failing: independent-projects/tools/devtools-common 
! Skipped: core/deployment core/runtime devtools/cli and 813 more

📦 independent-projects/tools/devtools-common

✖ io.quarkus.cli.plugin.PluginManagerUtilTest.shouldGetPluginFromAliasedLocation line 77 - History - More details - Source on GitHub

java.lang.IllegalStateException: Could not determinate name for location.
	at io.quarkus.cli.plugin.PluginManagerUtil.lambda$getName$9(PluginManagerUtil.java:95)
	at java.base/java.util.Optional.orElseThrow(Optional.java:403)
	at io.quarkus.cli.plugin.PluginManagerUtil.getName(PluginManagerUtil.java:95)
	at io.quarkus.cli.plugin.PluginManagerUtil.fromLocation(PluginManagerUtil.java:40)
	at io.quarkus.cli.plugin.PluginManagerUtil.fromAlias(PluginManagerUtil.java:58)
	at io.quarkus.cli.plugin.PluginManagerUtilTest.shouldGetPluginFromAliasedLocation(PluginManagerUtilTest.java:77)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 extensions/smallrye-reactive-messaging-kafka/deployment

✖ io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase.sseStream - History

• Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase Expecting size of: [] to be greater than or equal to 2 but was 0 within 10 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: 
Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase 
Expecting size of:
  []
to be greater than or equal to 2 but was 0 within 10 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)

---

⚙️ Native Tests - Messaging1

📦 integration-tests/reactive-messaging-kafka

✖ io.quarkus.it.kafka.KafkaConnectorIT.testFruits - History

• Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <5> within 10 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <5> within 10 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
	at io.quarkus.it.kafka.KafkaConnectorTest.testFruits(KafkaConnectorTest.java:63)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)

[geoand]

That Windows failure looks suspicious