Incorrect timezone display in BarViz

### Context
In the subscription trigger outcomes page, the Date column displays a "X hours ago" value, as well as a tooltip that shows the absolute time (eg: Date displays "4 hours ago", tooltip displays "2:33am"). These dates don't match up with the user machine's local time.

Eg:
```
Subscription trigger outcome: 4 hours ago
Tooltip: 2:23am
User local time: 9:23am
```

It could be because the tooltip displays the server's local time, based on the deployed PCS instance.

This makes it harder to work with the subscription history triggers, especially when coupled with other already ambiguous datetime displays like the one in Azure Data Explorer

### Goal
If possible, match the "X hours ago" and tooltip time display with the user's timezone.
Look for any other places in BarViz where this issue might also exist.

Start at the BarViz subscription trigger outcomes page and trace how the Date column's relative value and tooltip are rendered. Check other BarViz date displays for the same behavior; this is done when both values use the user's local timezone consistently.

Written by the indexing model from the issue text.