Appended timezone to publish_on and unpublished_on field

Assigning to myself to work on 2.x-dev branch.

Rerolled. Removes the STRONG tag and fixes some coding standards.

The placement of the text beside the time field can be a little off. I wonder if it'd be better to just have a single comment at the top of the fieldset that said e.g. "All times are in [timezone]" rather than adding a suffix on each field?

Does the timezone problem boil down to some timezone translation that core is performing on the field? This site is configured to run in America/Chicago, I'm in America/New_York; when I load the form the browser defaults to e.g. 12:30pm, but when I then save the form a value of 12:30pm becomes 11:30am.

Thanks @DamienMcKenna for re-rolling. Yes I like your idea of a single comment at the top of the fieldset.
If you want to convert to a MR then please do that, as then we will see the phpunit tests even when there are phpcs errors that need fixing.

Your MR127 was many commits behind the current 2.x dev branch and the initial pipelines were running with old code, had fewer test jobs, and the cspell & phpstan were failing. I didn't when the issue fork was created, but if that was a while ago it would explain this. I simply added a comment /rebase to the MR overview page and this rebased the branch, no problem. You can see the pipeline now has more jobs, but all pass green.

This is a UI change.

How about going a step further and just showing what the current time is according to the server, so that the person can know what time they're working in relation to?