Timezone conversion issues

[erwindon]

Describe the bug
As seen in the attached screenshot below (done on Firefox on Windows Server 2019), the timestamp in the white below the job name shows 1:24 EDT, while the output within the black output shows the timestamp as 9:24 EDT. That matches the 4 hour difference that EDT applies to UTC (UTC-4).

Screenshots

Additional context
New issue stemming out of testing for #485

[erwindon]

welcome back! good that you treat this as a separate issue.
I don't have the opportunity to act on this one as quickly as the previous one. please be patient...

In the image I see another small issue: the field "__state_ran__" is superfluous and should be hidden. In general SaltGUI keeps the details from the states small by eliminating trivial information. e.g. something that you don't see is the duration of second task because it was less than 10 milliseconds (but it is still counted for the total duration).

[erwindon]

changed to PR
first commit is only about 'state_ran'

[mkbrown]

state_ran is now hidden, so first commit works as intended. No worries on the issue itself; just reporting it since I'm in the weeds. I'm teaching myself salt for work stuff, and porting Puppet and Ansible code to it, so lots to keep myself amused... ;-p

Have a great week!

/Mike

[erwindon]

cherry-picked the commit for "state_ran" to the main branch
restarted this PR with an empty branch (that confused github a bit, but the PR is open again)

[erwindon]

the field "start_time" (on task level) is implemented by SaltStack as a local-time.
but field "StartTime" (on job level) is derived from the job-id, which is implemented by SaltStack as utc-time.

[erwindon]

(re-opened after accidental close)

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[erwindon]

added information line at the top of the high-state output to inform user of interpretation of the timestamp