Replace inefficient new String() constructors in GetterIT.testSSOAuthExistingUserRelogin

Summary

The code-quality bot (CodeQL on #816) flags two "Inefficient String constructor" instances in src/it/java/dbProcs/GetterIT.java, inside testSSOAuthExistingUserRelogin():

• String userName = new String("SSOReloginUser Lastname"); → String userName = "SSOReloginUser Lastname";
• String ssoName = new String("ssoreloginuser@example.com"); → String ssoName = "ssoreloginuser@example.com";

new String("literal") creates a redundant object; assign the literal directly. No behavior change, no new imports.

Severity

Trivial — test-only, micro-efficiency. Good first issue.

Acceptance criteria

• Both new String("...") calls in testSSOAuthExistingUserRelogin() replaced with direct literal assignment.
• GetterIT still passes; code-quality alerts cleared.

Context

Surfaced while reviewing the code-quality bot output on #816. Out of scope for the connection-pooling work; filed as a standalone follow-up. Not a blocker for #816.

Open src/it/java/dbProcs/GetterIT.java and locate testSSOAuthExistingUserRelogin(). Replace the two specified new String(...) assignments with direct literals, then run GetterIT and confirm the code-quality alerts are cleared.