Refactor Post Date Relative Time Rendering for Future Dates

[amitraj2203]

What?

Fixes: #62976

Why?

When you have a Date block on a post, schedule the post to the future, and then preview the post, the Date block shows a past date, even though the editor showed a relative future-tense date.

How?

This PR modifies the post date block's relative time format rendering logic to correctly display future dates using %s from now format alongside existing %s ago handling.

Testing Instructions

1. Add the Date Block
2. Select the last option in CHOOSE A FORMAT
3. Schedule the post for a future date
4. Preview the post

Screenshots or screencast

Screen.Recording.2024-06-28.at.7.55.55.PM.mov

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: amitraj2203 <[email protected]>
Co-authored-by: noisysocks <[email protected]>
Co-authored-by: t-hamano <[email protected]>
Co-authored-by: mrfoxtalbot <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[noisysocks]

Do we need to update the Comment Date block as well?

[amitraj2203]

I don't think so, as this case is only for when a post is scheduled for future date.

[t-hamano]

Looks good to me.

By the way, I noticed a while ago that when the time is displayed in minutes, the editor displays it as "minute/minutes", but the front end uses the abbreviation (min/mins). This is because the human_time_diff() function uses an abbreviation only for "minutes". This issue was addressed by the following core ticket:

https://core.trac.wordpress.org/ticket/61535

[noisysocks]

Thanks again @amitraj2203