FindResourceWriters often creates HashSets and ArrayLists while not necessary

[franz1981]

This is preventing to create to allocate memory of some common scenarios found while using Multi<T> in an endpoint, which involve streaming and perform this lookup (for T) for each element returned.

[quarkus-bot]

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

• title should preferably start with an uppercase character (if it makes sense!)

_{This message is automatically generated by a bot.}

[franz1981]

@geoand this should be a minor but stil save allocations in the hot path if complex mutiny pipelines are used (involving Multi, which shouldn't be that common TBH)

[geoand]

Thanks!

[geoand]

Can we fix this one and rebase it?

[geoand]

Imports need need to be sorted

[quarkus-bot]

Failing Jobs - Building ef07212

Status	Name	Step	Failures	Logs	Raw logs
✔️	Gradle Tests - JDK 11
✖	Gradle Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

✖ io.quarkus.gradle.devmode.ModuleWithParentDependencyDevModeTest.main line 14 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference, java.util.concurrent.atomic.AtomicReferencejava.lang.String, java.lang.Stringboolean was not fulfilled within 1 minutes  30 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)