Multi-select date-time filter — timestamp values missing seconds, causing duplicate/indistinguishable entries in the list

Nobody has claimed this yet.

**Description:**
-------------------------------------------------------------------
When a user opens the multi-select filter for a date-time field, the list displays all feature timestamps in `DD/MM/YYYY HH:MM` format. Seconds are truncated from the display.
As a result, multiple features recorded within the same minute appear as identical entries in the list, making it impossible for the user to distinguish between them or make a meaningful selection. This leads to incorrect filtering results, potential unintended data actions, and an unusable list in larger datasets.

**Environment**
-----------------------------------------------------------------
[x ] Staging [x] PROD

**Application:**
-----------------------------------------------------------------
iOS 26.5 / Android 15

**Steps to Reproduce:**
--------------------------------------------------------------------
_1. Open project **tester-ws-1/preview_mode_bug** containing a layer with a date-time type field.
2. Open the Filters panel.
3. Tap on a multi-select filter for a date-time field (Multi-select-POI-date-time filter)
4. Observe the list of values displayed._

**Expected Result:**
-------------------------------------------------------------------
Timestamps are displayed with full precision including seconds `(DD/MM/YYYY HH:MM:SS`), allowing the user to distinguish between features recorded in the same minute. Selecting a specific timestamp applies the filter only to the exact matching feature(s).

**Actual Result:**
------------------------------------------------------------------
Timestamps are displayed as `DD/MM/YYYY HH:MM` only. Multiple features recorded within the same minute appear as duplicate identical entries (e.g., nine entries all showing 27/05/2026 14:35).

This causes the following issues:
**1. Incorrect filtering results**
When the user selects one of the duplicate entries, it is unclear which record is actually selected — or whether all records sharing that truncated timestamp are selected.
**2. Data loss risk during selection**
If a user is trying to isolate one specific feature (e.g., to review or edit it), selecting a visually duplicate timestamp may unintentionally include multiple features. In a field data collection context, acting on the wrong feature could lead to incorrect data being modified or submitted.

**Attachments:**
--------------------------------------------------------------------
Screenshot showing duplicate 27/05/2026 14:35 entries in the multi-select list.

Reproduce the issue in tester-ws-1/preview_mode_bug by opening the Filters panel and the Multi-select-POI-date-time filter on iOS or Android. Trace the entry point that formats date-time filter values and verify that the list distinguishes timestamps recorded within the same minute and that selecting one applies only to the exact matching feature.

Written by the indexing model from the issue text.