fix: Show "Publish Immediately"

[tofumatt]

Depends on #7621.

• Close Publish date uses draft create date and not updated on publish #7195
• Close Show "Publish: Immediately" as date for new drafts without a date #8395
• Close When scheduling a post to publish, not possible to change and publish immediately #9030
• Close Show "Publish: Immediately" for new drafts by inferring floating date #9967
• Fix Post never appears as set to publish "immediately" #10182

Description

Shows "Publish: Immediately" if the publishing date for the post is now or before now.

How has this been tested?

Tested locally and included E2E tests.

Screenshots

Will come after #7621 is merged...

[pento]

I don't think this is the correct behaviour: the author can actively choose a publication date in the past, in which case it should show that.

[tofumatt]

Why should we show the exact date in the past though? The effect is that it will be published immediately. The published date will still be set to be in the past, but it will go live immediately.

I guess if we do that already we want to, but it's an odd UX to me 🤷‍♂️

(At any rate the E2E tests here should at least be added because this seems to be a regression; we used to show "immediately" but no longer do and we didn't have anything to catch that.)

[earnjam]

After discussing this one pretty extensively on the core REST API side, we came to the agreement that the best solution would be the method in #9967. It fixes the publish date label problem in while maintaining consistency with the UX of the classic editor.

[kadamwhite]

+1 on @earnjam's note; and from a UX perspective, if you intentionally back-date a post that feels like important information to communicate. Otherwise we'd end up having people expect it to be published "Immediately", but then find it's several pages back in their archives if the date is a ways back.

[kadamwhite]

Closing this in favor of #9967