Sync retry message shows time as "4:04PM" with no date or timezone #29535

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

When a sync operation fails and is scheduled for a retry, the operation message tells you when the next attempt happens, but formats the time with Go's time.Kitchen layout:

ComparisonError: Failed to load target state: failed to generate manifest for
source 1 of 1: rpc error: code = Unavailable desc = connection error: desc =
"transport: Error while dialing: dial tcp 10.0.9.23:8081: connect: connection
refused". Retrying attempt #2 at 4:04PM.

Here, 4:04PM is not enough to act on:

• No date, so you can't tell whether it's today or (near midnight) tomorrow.
• No timezone, so you can't tell if it's the controller's clock or your own.
• No indication of what time "now" is, so you can't tell whether the retry is seconds away or an hour away which is the thing you actually want to know.

To Reproduce

1. Create an Application with a retry strategy, e.g.:

   spec:
     syncPolicy:
       retry:                                                                 
         limit: 5
         backoff:
           duration: 2m
           maxDuration: 1h

2. Make the sync fail (for example, point it at an unreachable repo-server or an invalid project).
3. Look at .status.operationState.message on the Application, or the message shown in the UI.

Expected behavior

The message should say how long the wait is, and give an absolute time that can't be misread as local time. For example:

... connection refused. Retrying attempt #2 in 2m0s (at 2026-09-03T16:04:00Z).

Screenshots

N/A

More details here - https://cloud-native.slack.com/archives/C020XM04CUW/p1788278865234229