Event triggers created_at time shifted +09:00

Nobody has claimed this yet.

### Version Information

Server Version: v2.40.0

### Environment

OSS

### What is the current behaviour?

The created_at values displayed on the Processed Events page and Invocation Logs page in the Hasura Console are offset by 9 hours.

### What is the expected behaviour?

The values should display the actual time when the events were executed (i.e., the values should reflect the time 9 hours earlier).

### How to reproduce the issue?

1. Create an event that triggers when data is INSERTed into any table.
2. Perform an INSERT operation on the table.
3. Check the logs on the Hasura Console's Events page.

### Screenshots or Screencast



### Please provide any traces or logs that could help here.

Event payload:
```
{
"headers": [
{
"name": "Content-Type",
"value": "application/json"
},
{
"name": "User-Agent",
"value": "hasura-graphql-engine/v2.40.0"
}
],
"payload": {
"created_at": "2024-06-24T14:22:32.128413",
"delivery_info": {
"current_retry": 0,
"max_retries": 0
},
"event": {
"data": {
"new": {
:(snip)
```

### Any possible solutions/workarounds you're aware of?

Execute the following SQL commands:
```
ALTER TABLE hdb_catalog.event_invocation_logs
ALTER COLUMN created_at TYPE TIMESTAMPTZ;

ALTER TABLE hdb_catalog.event_log
ALTER COLUMN created_at TYPE TIMESTAMPTZ;
```

Ref.
https://github.com/hasura/graphql-engine/issues/5722

### Keywords

event trigger, time zone, TIMESTAMPTZ

Start with the Hasura Console's Processed Events and Invocation Logs pages, then inspect the event_invocation_logs and event_log created_at columns referenced in the workaround. Reproduce an INSERT-triggered event and compare the displayed time with the event payload. Done means both pages show the actual execution time without the nine-hour offset, with coverage for the affected timestamp handling.

Written by the indexing model from the issue text.