Description of problem:

foreman tasks follows system time instead of time on user-profile

How reproducible:

always

Is this issue a regression from an earlier version:

yes

Steps to Reproduce:

1. modify system time on satellite server using 'timedatectl set-time <>'

2. run test job run from satellite

3.

Actual behavior:
If modified time is ahead of earlier time, task page will show "start and end time" as future reference

if modified time is behind the earlier time, task page will show "start and end time" as past reference

Expected behavior:
Instead of referencing system time for task, it should reference timezone set based on user-profile on satellite

Business Impact / Additional info:

old bug: https://bugzilla.redhat.com/show_bug.cgi?id=1253376