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.

git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1555702 13f79535-47bb-0310-9956-ffa450edef68
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.

Only use UTC if the database has been upgraded to 10.11 format, so
that the change won't cause problems on downgrade.

git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1555703 13f79535-47bb-0310-9956-ffa450edef68