Different behavior in TestIdentityAssociation for getDeferredIdentity and getIdentity

[vonatzigenc]

Describe the bug

The logic in io.quarkus.test.security.TestIdentityAssociation for getDeferredIdentity and getIdentity is different. This results in certain situations where the SecurityIdentity read via getDeferredIdentity() is different from the SecurityIdentity obtained via getIdentity().

The getIdentity method was adjusted with e1f50c1 , but the getDeferredIdentity wasn't.

Expected behavior

TestIdentityAssociation.getDeferredIdentity().await().indefinitely() always equals TestIdentityAssociation.getIdentity()

Actual behavior

TestIdentityAssociation.getDeferredIdentity()` always returns the testIdentity if one exists.

TestIdentityAssociation.getIdentity() checks the underlying identity first.

How to Reproduce?

I do not have a reproducer project. But can be isolated relatively easily.

1. Call SecurityIdentityAssociation#setIdentity (with SecurityIdentity that isn't anonymous)
2. Result of getIdentity differs from getDeferredIdentity().await().indefinitely()

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.15.1.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response