Time Format is wrong in Data Explorer + Customize does not apply

__Steps to reproduce:__
List the minimal actions needed to reproduce the behaviour.

Start influxdb docker container, e.g.

```
docker run -d \
--name influxdb \
--restart=unless-stopped \
--network=host \
-e TZ=Europe/Berlin \
-p 8086:8086 \
-v /my/path/to/influxdb:/var/lib/influxdb2 \
influxdb:latest
```

1. Go to Data Explorer and submit any query.
2. Click on Customize

__Expected behaviour:__
The Time Format can be customized and the values are shown correctly.

__Actual behaviour:__
The Time Format seems to be not applied correctly.
e.g. (Note: if my Expected values are wrong please let me know, then I can adapt them in the table)
| Time Format | Actual | Expected |
|-------------------------------|-------------------------------------|----------------------------------------|
| YYYY-MM-DD HH:mm:ss | 2023-10-21 05:26:40 GMT+2 | 2023-10-21 17:26:40 |
| YYYY-MM-DD hh:mm:ss a ZZ | 2023-10-21 05:26:40 GMT+2 | 2023-10-21 5:26:40 PM GMT+2 |
| DD/MM/YYYY HH:mm:ss.sss | 21/10/2023 05:26:40.000 | 21/10/2023 17:26:40.000 |
| DD/MM/YYYY hh:mm:ss.sss a | 2023-10-21 05:26:40 GMT+2 | 21/10/2023 05:26:40.000 PM |
| MM/DD/YYYY HH:mm:ss.sss | 10/21/2023 05:26:40.000 | 10/21/2023 17:26:40.000 |
| MM/DD/YYYY hh:mm:ss.sss a | 2023-10-21 05:26:40 GMT+2 | 10/21/2023 05:26:40.000 PM |
| YYYY/MM/DD HH:mm:ss | 2023/10/21 05:26:40 | 2023/10/21 17:26:40 |
| YYYY/MM/DD hh:mm:ss a | 2023-10-21 05:26:40 GMT+2 | 2023/10/21 05:26:40 PM |
| HH:mm | 05:26 | 17:26 |
| hh:mm a | 5:26 PM | |
| HH:mm:ss | 05:26:40 | 17:26:40 |
| hh:mm:ss a | 2023-10-21 05:26:40 GMT+2 | 05:26:40 PM |
| HH:mm:ss ZZ | 05:26:40 GMT+2 | 17:26:40 GMT+2 |
| hh:mm:ss a ZZ | 2023-10-21 05:26:40 GMT+2 | 05:26:40 PM GMT+2 |
| HH:mm:ss.sss | 05:26:40.000 | 17:26:40.000 |
| hh:mm:ss.sss a | 2023-10-21 05:26:40 GMT+2 | 05:26:40.000 PM |
| MMMM D, YYYY HH:mm:ss | October 21, 2023 05:26:40 | October 21, 2023 17:26:40 |
| MMMM D, YYYY hh:mm:ss a | 2023-10-21 05:26:40 GMT+2 | October 21, 2023 05:26:40 PM |
| dddd, MMMM D, YYYY HH:mm:ss | Saturday, October 21, 2023 05:26:40 | Saturday, October 21, 2023 17:26:40 |
| dddd, MMMM D, YYYY hh:mm:ss a | 2023-10-21 05:26:40 GMT+2 | Saturday, October 21, 2023 05:26:40 PM |

__Environment info:__

Host Info: Ubuntu 22.04 with Linux 6.2.0-35-generic x86_64

* Please provide the command you used to build the project, including any `RUSTFLAGS`.
* System info: Run `uname -srm` or similar and copy the output here (we want to know your OS, architecture etc).
* If you're running IOx in a containerised environment then details about that would be helpful.
* Other relevant environment details: disk info, hardware setup etc.

__Config:__
Copy any non-default config values here or attach the full config as a gist or file.

__Logs:__
Include snippet of errors in logs or stack traces here.
Sometimes you can get useful information by running the program with the `RUST_BACKTRACE=full` environment variable.
Finally, the IOx server has a `-vv` for verbose logging.

Start by reproducing the issue in Data Explorer: submit a query, open Customize, and compare the displayed values with the listed formats. Trace the frontend code behind Data Explorer and Customize to find where time formatting is applied. Done means each listed format is honored and the customization changes the displayed timestamps.

Written by the indexing model from the issue text.