fix: Using current time in UTC as default in Postgresql

Using current time in UTC as default in Postgresql for created and modified time.

Signed-off-by: bruce <[email protected]>

cmd/core-keeper/res/db/sql/01-tables.sql

@@ -8,8 +8,8 @@ CREATE TABLE IF NOT EXISTS core_keeper.config (
     id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
     key TEXT NOT NULL,
     value TEXT NOT NULL,
-    created timestamp NOT NULL DEFAULT now(),
-    modified timestamp NOT NULL DEFAULT now()
+    created timestamp NOT NULL DEFAULT (now() AT TIME ZONE 'utc'),
+    modified timestamp NOT NULL DEFAULT (now() AT TIME ZONE 'utc')
 );
 
 -- core_keeper.registry is used to store the registry information

cmd/support-scheduler/res/db/sql/01-tables.sql

@@ -17,5 +17,5 @@ CREATE TABLE IF NOT EXISTS support_scheduler.record (
     action JSONB NOT NULL,
     status TEXT NOT NULL,
     scheduled_at timestamp NOT NULL,
-    created timestamp NOT NULL DEFAULT now()
+    created timestamp NOT NULL DEFAULT (now() AT TIME ZONE 'utc')
 );