Improve date format in status report EOL message

Improved the date format to suggested more human readable format "November 2023" in status report EOL message

Please review, moved to NR.

Seems straight forward enough.

Rebased the MR with latest code, seems fine

Yes, when just the month and year are displayed the proposed resolution is easier to read. The other messages tested in the same test have Year, month, and date so they do not need to be changed.

Leaving at RTBC

Rebased MR with latest code, seems working fine.

Committed/pushed to 11.x, 11.0.x and 10.4.x, thanks!

catch → closed merge request !8507

Looks like my feedback from the previous issue did not make it into the IS here.

As I pointed out on the issue that this was split off from, the original date formats were chosen to be reasonably understandable without having to get international localization etc. involved for a status report message, but then trying to mitigate the readability again afterward with the month abbreviation, and I think both might have been wrong. (The original convo went something like: "We shouldn't use an American date format because it could confuse people internationally" "Well, year-first is unambiguous" "Ahh but hmm numbers only are harder to read/scan/understand" etc,

For this issue's change: Why is "2023-Nov-30" okay but not "2023-Nov"?

We should test it in (a) a language that uses the Gregorian calendar but not US date formats and (b) a language that doesn't necessarily use the Gregorian calendar (Arabic or Hindi maybe), and consider a more complete fix.

For #17 (manual testing with multilingual/localization awareness).

(We might later want feedback from date or localization maintainers to make sure we're using the APIs correctly since it was always sort of a hack and so far this changes the specific format in the hack, but we might also be able to figure that out just from the testing.)

Not sure if this could be related 📌 Use easily recognizable date format RTBC

But @xjm since that one got product sign off could we use the same format here?

Since 📌 Use easily recognizable date format RTBC was accepted and merged think we should do the same here.