Fixing TCK deadlock

- TCK authentication tests ended in deadlock, because the TCK client steals
  logging.properties from the server (wrong idea, 3 JVMs using same
  file - server.log).
  It is because GlassFishLogHandler redirects standard output streams to the
  server.log file, then SimpleLogHandler uses new streams, which situation
  leads to a deadlock.
- GJULE LogManager prevents that by saving original streams on startup, so
  whatever happens later, it still has original values available. JUL doesn't
  have this mechanism.
- So in this commit I am just switching the order, so SimpleLogHandler is
  configured first with original values.
- However, this commit doesn't fix the issue where TCK steals server's cfg file.

Signed-off-by: David Matějček <david.matejcek@omnifish.ee>

nucleus/admin/template/src/main/resources/config/logging.properties

@@ -18,8 +18,8 @@
 # Handler settings
 
 handlers=\
-org.glassfish.main.jul.handler.GlassFishLogHandler,\
 org.glassfish.main.jul.handler.SimpleLogHandler,\
+org.glassfish.main.jul.handler.GlassFishLogHandler,\
 org.glassfish.main.jul.handler.SyslogHandler
 
 org.glassfish.main.jul.handler.GlassFishLogHandler.buffer.capacity=10000