Cloud Config date converts to object

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

When adding a Cloud Config param of type "Date", then refreshing the dashboard page, the date object is displayed incorrectly as an object.

Steps to reproduce

1. Add Cloud Config param of type "Date".

2. Set a date value:
   

3. Create param; date value is stored as 2024-05-05T00:36:00.000Z:
   

4. Refresh browser page; date value is stored as {"__type":"Date","iso":"2024-05-05T00:36:00.000Z"}:
   

   The date value is displayed as a date object, which should not happen.

5. Edit the param; the date object value appear, can be edited and saved.
   

   If pasting the previous value string 2024-05-05T00:36:00.000Z, the save button is disabled, because this string cannot be saved directly despite being displayed in step 3.

Analysis

• When first creating the param, the date value shows a date picker. Afterwards, the date is shown in text form, either as date string or date object. Instead of showing the date in 3 different forms, a single form should be chosen. The text form is the preferred form, because text can be copied/pasted and a date value can be defined in full detail (microseconds, time zone, etc).
• A date picker can be offered in addition to the text field for easer date entry, by clicking on a calendar icon.
• To make it easier to enter a date value for users who are not familiar with the ISO format, the ISO format should be displayed as placeholder when the value field is empty, or in the description field on the side.

Environment

Dashboard

• Parse Dashboard version: 6.0.0-alpha.6
• Browser (Safari, Chrome, Firefox, Edge, etc.): Safari
• Browser version: Version 17.4.1 (19618.1.15.11.14)

Reproduce the issue in the Parse Dashboard by creating a Cloud Config parameter with type Date, refreshing the page, and editing the value. No source files or tests are named in the issue, so first locate the Cloud Config parameter editor and its date-value handling. Done means the value remains consistently editable and displayable after refresh without exposing the Parse date object or disabling valid ISO-string saves.