chore: revert debug logging after the auth issue was diagnosed

Found the actual issue was a stale Docker image in the LXC (the CI
runner was stuck for ~30h starting at task 323 on Aug 14). The newly
pulled image with all prior fixes (no @Authenticated, records w/
@RegisterForReflection, create-drop for tables) has been verified
end-to-end: login returns 200, /me returns 200 with the user,
change-password returns 200 after password validation.

So we can drop the LOG statements and the SQL debug log without
regressing anything.

src/main/resources/application.properties

@@ -9,9 +9,7 @@ quarkus.datasource.jdbc.url=jdbc:h2:file:./data/shots;DB_CLOSE_DELAY=-1
 quarkus.datasource.username=sa
 quarkus.datasource.password=
 quarkus.hibernate-orm.database.generation=create-drop
-quarkus.hibernate-orm.log.sql=true
-quarkus.log.category."org.hibernate.SQL".level=DEBUG
-quarkus.log.category."com.l2.shots.auth".level=DEBUG
+quarkus.hibernate-orm.log.sql=false
 
 # JWT
 mp.jwt.verify.issuer=shot-crafter-calculator