Issue Summary: 

JCMA Preflight needs to check the jira.date.picker.java.format on cloud and see if that is valid format, else let customer know that this will cause a data loss 

Steps to Reproduce

Pre-requisites

1. Jira Data Center (source) has jira.date.picker.java.format from Jira system advanced settings correctly configured as yyyy/MM/dd (uppercase M as months).
2. Jira Cloud (target) has the same setting incorrectly configured as yyyy/mm/dd (lowercase m as minutes).

Steps

1. Create a custom field of type date, for example, "Delivery Date"
2. Create multiple issues with custom field "Delivery Date" as 2026/07/08 (no values containing `01`)
3. Set values for system fields such as "Due Date" as 2026/07/02 (no values containing `01`)
4. Migrate issues where issues have "Delivery Date" custom field and "Due Date" (both of type date) using JCMA.
   Tested using JCMA 1.17.1
5. Observe same issue in Jira Cloud.
   The values seem to have been changed during the import phase as they were in the correct format when exported.

Expected Results

Date values should remain the same as when exported, OR
There should be a preflight check to warn the user of incorrect date format which may cause data loss.

Actual Results

All date fields incorrectly display the month as January.

Workaround

Currently there is no known workaround for this behavior after the migration
This can be prevented by checking the date time value configuration or restoring the default.