DERBY-6387: Incorrect ordering of triggers in dblook

Order the triggers by the CREATIONTIMESTAMP column so that dblook
produces a script that recreates the triggers in the same order as
they were originally created.

git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1551940 13f79535-47bb-0310-9956-ffa450edef68
DERBY-5866: Triggers fire out of order

Make sure the creation timestamp of a newly created trigger is higher
than the timestamps of the existing triggers on the same table. If it
is not higher, the triggers may fire in the wrong order. If the
current timestamp is not higher than the timestamp of the previous
trigger defined on the table, the new trigger now gets a creation
timestamp that is one millisecond higher than the creation timestamp
of the previous trigger.
DERBY-5866: Triggers fire out of order

In order to avoid ambiguities around switch from daylight saving time
to standard time, and other time zone changes, store the trigger
creation timestamps in Coordinated Universal Time (UTC) instead of the
local time zone.