feat: Send editor feedback

[dcalhoun]

Collecting feedback from users while in editor may uncover valuable
insights.

Related:

• https://github.com/Automattic/dotcom-forge/issues/10125
• feat: Send editor feedback WordPress-iOS#23980

To Test:

1. Open the experimentla editor.
2. Tap the more button (three vertical dots) in the top-right corner.
3. Tap Send Feedback.
4. Submit feedback.
5. Verify its delivery within the customer support system.

Regression Notes

1. Potential unintended areas of impact
   None likely with this limited addition.
2. What I did to test those areas of impact (or what existing automated tests I relied on)
   N/A
3. What automated tests I added (or what prevented me from doing so)
   N/A

PR Submission Checklist:

• I have completed the Regression Notes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Testing Checklist (strike-out the not-applying and unnecessary ones):

• WordPress.com sites and self-hosted Jetpack sites.
• Portrait and landscape orientations.
• Light and dark modes.
• Fonts: Larger, smaller and bold text.
• High contrast.
• Talkback.
• Languages with large words or with letters/accents not frequently used in English.
• Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
• Large and small screen sizes. (Tablet and smaller phones)
• Multi-tasking: Split screen and Pop-up view. (Android 10 or higher)

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr21586-f4bde50
	Commit	f4bde50
	Direct Download	jetpack-prototype-build-pr21586-f4bde50.apk

Note: Google Login is not supported on these builds.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr21586-f4bde50
	Commit	f4bde50
	Direct Download	wordpress-prototype-build-pr21586-f4bde50.apk

Note: Google Login is not supported on these builds.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Project coverage is 39.48%. Comparing base (e72074a) to head (f4bde50).
Report is 62 commits behind head on trunk.

Files with missing lines	Patch %	Lines
...ava/org/wordpress/android/ui/ActivityLauncher.java	0.00%	3 Missing ⚠️
...roid/ui/main/feedbackform/FeedbackFormViewModel.kt	0.00%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##            trunk   #21586   +/-   ##
=======================================
  Coverage   39.48%   39.48%           
=======================================
  Files        2117     2117           
  Lines       99464    99464           
  Branches    15296    15296           
=======================================
  Hits        39269    39269           
  Misses      56714    56714           
  Partials     3481     3481           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nbradbury]

@dcalhoun This works well, but I'm wondering if we need to include something that tells us the feedback was sent from the editor? Perhaps something as simple as adding "Editor feedback: " to the beginning of the feedback text?

[dcalhoun]

This works well, but I'm wondering if we need to include something that tells us the feedback was sent from the editor? Perhaps something as simple as adding "Editor feedback: " to the beginning of the feedback text?

Yeah, I think that is a good idea. I'll explore flagging the feedback, with a prefix or otherwise.

[dcalhoun]

@nbradbury I added an [Editor] prefix for feedback submitted from within the editor in f4bde50. Let me know what you think of the prefix and implementation. Thanks!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[nbradbury]

I added an [Editor] prefix for feedback submitted from within the editor

I think that's fine! I'll approve this and leave it to you to merge.

[nbradbury]