E2E: Split list view keyboard shortcuts into multiple tests

[yogeshbhutkar]

What, Why and How?

Part of #64305

This PR splits List View > should cut, copy, paste, select, duplicate, insert, delete, and deselect blocks using keyboard into the following tests:

1. should duplicate block using keyboard
2. should copy and paste blocks using keyboard
3. should cut and paste blocks using keyboard
4. should select and deselect blocks using keyboard
5. should insert and delete blocks using keyboard

Testing Instructions

1. In a local environment, run the following command:

npm run test:e2e -- /test/e2e/specs/editor/various/list-view.spec.js

2. Confirm all the tests corresponding to the list-view.spec.js pass.

Screenshot

[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] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core, Gutenberg Plugin.
• Labels found: [Type] Automated Testing, [Type] Code Quality.

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]

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: yogeshbhutkar <[email protected]>

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