Replace deprecated methods and classes in Quarkus Security and tiny bit of refactoring

[michalvavrik]

Changes:

• stop using AnnotationsTransformer constructor marked for removal
• stop storing SecurityCheckStorage as static volatile variable on recoreder as we dont' need it there
• replecate deprecated io.smallrye.mutiny.groups.UniAndGroupIterable#combinedWith(java.util.function.Function<java.util.List<?>,O>) as it is marked for removal
• reduces usage of raw types in QuarkusIdentityProviderManagerImpl, it's not great, but hopefully result is bit better
• marking io.quarkus.security.spi.AdditionalSecuredClassesBuildItem for removal, it has been deprecated since 2.15
• NativeOrNativeSourcesBuild is deprecated, IMO we could always produce the NativeImageFeatureBuildItem and Quarkus should take care of it. Nevertheless, in order to keep original behavior, I replaced it with the quarkus.native.enabled config property

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 7a710f0.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17 Windows

📦 extensions/resteasy-reactive/rest-client/deployment

✖ io.quarkus.rest.client.reactive.stork.StorkResponseTimeLoadBalancerTest.shouldUseFasterService - History

• expected: "hello, Alice" but was: "hello, I'm a slow server" - org.opentest4j.AssertionFailedError

org.opentest4j.AssertionFailedError: 

expected: "hello, Alice"
 but was: "hello, I'm a slow server"
	at io.quarkus.rest.client.reactive.stork.StorkResponseTimeLoadBalancerTest.shouldUseFasterService(StorkResponseTimeLoadBalancerTest.java:58)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at io.quarkus.test.QuarkusUnitTest.runExtensionMethod(QuarkusUnitTest.java:513)
	at io.quarkus.test.QuarkusUnitTest.interceptTestMethod(QuarkusUnitTest.java:427)

[sberyozkin]

To me it looks like it is becoming less obvious what the actual var type is, we'll have no idea what providers are when we look at this code in 6 months :-), I don't really mind, I'm just not sure about across the board replacement of local type references with var...

[michalvavrik]

I changed this because List<IdentityProvider> is a raw type and var is shorter to write :-) I don't give importance to things like these, for me it's like a book. I'll add it back (with a wildcard) because if it is better readable for someone like you, it should be there.

[sberyozkin]

@michalvavrik It is ok, you don't have to...

[michalvavrik]

NP, I am finishing other PR, so if this one is not merged in an hour, I'll change it. One way or another thanks.