Fixes #445

Previously, the `get_post_status_friendly_name` function was retreiving the WordPress built-in Post Statuses and the Custom Statuses set within the plugin interface.  If you happen to register a post status another way, it would not appear in the Status Column of your Post Type.

This fix simplifies the logic to just get all the post stati, built-in, registered through the plugin interface, and registered on their own.  It returns the label that was set for each status.

Stop using `get_post_status_friendly_name`

Get custom post statuses in the Calendar view and in the ICS file

Instead of changing this function entirely, let’s just stop using it.  This commit puts it back to what it used to be so that Email Notifications can still use it.

Get the post status label directly instead of using a helper function

Function is no longer needed

Get all statuses for posts, filter all statuses, and make sure “Unpublished” accounts for custom statuses.

Get and filter all statuses for Story Budget.  Update the “Unpublished” status to account for these custom statuses.

In some instances, there will be a Post that has a Post State that is not it’s post status.  Example: Gutenberg, Liveblog.

We are filtering all post states with `check_if_post_state_is_status` and if a post’s post state does not match it’s post status, we will show it as a post state next to the title of the post.  The Post Status will remain in the Status column.

Need to check if it’s a new post and return if it is.

This prevents duplicate conditional statements and sets a value for $old_status_friendly_name so that New or Auto-Draft that had no previous value will have something valid.