Date display issue with multiple timezones

[Lelenaic]

* Describe the bug

When creating a date (without time) field in a general collection, the date is stored with a datetime with timezone format in PostgreSQL.
When someone in GMT+3 creates a record with a date 2024-05-21, PG stores "2024-05-20 21:00:00+00".
But when I display the date in GMT+2 in nocobase, I see 2024-05-20 (because the datetime is 2024-05-20 23:00:00 in GMT+2), but, it should still display 2024-05-21.

* Environment

• NocoBase version: v1.0.0-alpha.15

• PostgreSQL 16

• Deployment Methods: Docker

• Docker image version: latest

* How To Reproduce

1. Use postgresql
2. Create a general collection with a date field (without the time)
3. With a computer in a timezone, creates a record with a date.
4. See the record on a computer with a different timezone (smaller than the previous one, if created in GMT+3, see in +2).

Expected behavior

When the time is not displayed, the date should ignore the browser timezone to display the original date whatever the current user timezone is.
I've seen the PR #4366 talking about this issue but with an example about charts, but it should work like this everywhere.

[hongboji]

Sorry for not replying in time, we have discussed this issue and followed up with planning to resolve it

[MarekVigas]

Is there any update on this ? I have the same problem.

[zhouyanliang]

Is there any update on this ? I have the same problem.

Sitll in progress