feat: Separate pre-publish and post-publish panels visibility and settings

[snehapatil2001]

What?

This PR addresses the issue of confusion in the publishing flow where the user interface displays a checkbox in the post-publish panel. The checkbox, when unchecked, disables both the pre and post-publish panels, affecting the user experience.

Why?

Unchecking the only checkbox present disables both pre and post-publish panels, affecting the user's ability to receive suggestions and actions after publishing. The proposed changes aim to improve user understanding and provide a better user experience.

How?

The PR proposes to introduce two different settings to toggle their visibility. This separation allows users to control the display of each panel independently, providing a clearer and more intuitive experience. The changes also ensure that unchecking the checkbox in the post-publish panel only affects the post-publish suggestions, not both panels.

Testing Instructions

1. Open a post or page in the editor.
2. Navigate to the publishing flow.
3. Observe the presence and functionality of the "Always show pre-publish checks" checkbox in both pre and post-publish panels.
4. Check and uncheck the checkbox to verify its impact on the visibility of pre and post-publish panels.

Testing Instructions for Keyboard

Navigate through the publishing flow using the keyboard and perform the above steps to ensure accessibility and keyboard-only testing.

Screenshots

Screenshots or screencast

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @snehapatil2001! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[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: snehapatil2001 <snehapatil02@git.wordpress.org>

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