Fix: scheduler: handle last-rc-change values after Y2038

Resource history entries have a last-rc-change field with an epoch time.
Previously, this was parsed as a regular int for some status displays,
resulting in a Y2038 issue. Now, it is parsed using crm_element_value_epoch().

This only affected status displays, and not cluster operation.