Try: table+list view for responses and other Inbox UX explorations

[simison]

Context p1HpG7-wN7-p2

Proposed changes:

WIP several small and big improvements to the Inbox, including Table/List views, Gravatars, etc.

https://github.com/user-attachments/assets/ad1ad204-5ad3-4298-b5a7-0894d249e33b

This PR is mostly for testing, and improvements can be shipped in separate independent PRs.

Other information:

• [ ] Have you written new tests for your changes, if applicable?
• [ ] Have you checked the E2E test CI results, and verified that your changes do not break them?
• [ ] Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• Go to '..'

[github-actions[bot]]

Are you an Automattician? The PR will need to be tested on WordPress.com. This comment will be updated with testing instructions as soon the build is complete.

[github-actions[bot]]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• :white_check_mark: Include a description of your PR changes.
  
• :white_check_mark: Add a "[Status]" label (In Progress, Needs Review, ...).
  
• :red_circle: Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• :white_check_mark: Add testing instructions.
  
• :white_check_mark: Specify whether this PR includes any changes to data or privacy.
  
• :white_check_mark: Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation :robot:

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[jp-launch-control[bot]]

Code Coverage Summary

Coverage changed in 3 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/forms/src/dashboard/inbox/response.js	0/34 (0.00%)	0.00%	5 💔
projects/packages/forms/src/dashboard/inbox/dataviews/index.js	0/116 (0.00%)	0.00%	4 💔
projects/packages/forms/src/dashboard/inbox/dataviews/views.js	0/25 (0.00%)	0.00%	1 ❤️‍🩹

1 file is newly checked for coverage.

File	Coverage
projects/packages/forms/src/dashboard/inbox/copy-clipboard-button.jsx	0/15 (0.00%) 💔

Full summary · PHP report · JS report

_{If appropriate, add one of these labels to override the failing coverage check: https://github.com/Automattic/jetpack/labels/Covered%20by%20non-unit%20tests https://github.com/Automattic/jetpack/labels/Coverage%20tests%20to%20be%20added%20later https://github.com/Automattic/jetpack/labels/I%20don%27t%20care%20about%20code%20coverage%20for%20this%20PR}

[simison]

Split several findings of this exploration into new PRs:

• https://github.com/Automattic/jetpack/pull/44262
• https://github.com/Automattic/jetpack/pull/44242
• https://github.com/Automattic/jetpack/pull/44270
• https://github.com/Automattic/jetpack/pull/44264