Update error email heading to more clearly ask for details

[Nateowami]

We've gotten a lot of support emails where users did not provide any explanation about what went wrong. I believe this is for two reasons:

1. Not looking closely at the email and just hitting send
2. Misreading Please explain the problem. as a message to us, rather than instructions to the user.

I've updated the email so it starts with this message:

Please describe what you were doing when this error happened. Include:

• What you were trying to do
• What you expected to happen
• What actually happened
• Whether it happens every time, or only once

This is likely to address the second situation (misreading the heading), but not the first (not reading the email before sending).

---

This change is 

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.48%. Comparing base (10e1c38) to head (5882de7).
⚠️ Report is 1 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3537      +/-   ##
==========================================
+ Coverage   82.47%   82.48%   +0.01%     
==========================================
  Files         615      615              
  Lines       36935    36935              
  Branches     6033     6014      -19     
==========================================
+ Hits        30463    30467       +4     
- Misses       5572     5584      +12     
+ Partials      900      884      -16     

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

[RaymondLuong3]

@RaymondLuong3 reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @Nateowami)