[analytics] add error field to feedback event

[laushinka]

Description

[@jldec updated Aug 17, 2022]
The intent of this PR was to add the rendered error message along with the feedback tracking event, however, the object used in this implementation does not actually include the rendered error message, because that is derived in JSX.

With error	Without error

Related Issue(s)

Fixes #10402

How to test

1. Trigger an error when creating a workspace (steps here).
2. Visit Segment and filter for feedback_submitted.
3. See the error_rendered body.
4. Send a non-error feedback and see no error_rendered field on Segment.

Release Notes

NONE

• /werft with-preview
• /werft analytics=segment|TEZnsG4QbLSxLfHfNieLYGF4cDwyFWoe

[laushinka]

/werft run

👍 started the job as gitpod-build-laushinka-send-error-message-with-10402.1
(with .werft/ from main)

[jldec]

I think we should try to include the actual error text in the feedback report

Information about the context would be good too e.g. to tell the difference between 404 errors in say
a. starting a workspace from a repo URL context
vs.
b. starting a workspace from a snapshot URL

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[werft-gitpod-dev-com]

started the job as gitpod-build-laushinka-send-error-message-with-10402.4 because the annotations in the pull request description changed
(with .werft/ from main)

[jldec]

@laushinka I rebased and updated the werft flags in the description

[jldec]

Testing error reporting on workspace start with private repo

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jldec]

This implementation works, but it is incomplete because the error message text is not included with the feedback.
We either have to grab an image, or (better), extract the error message text as a string.

Currently, error handling implementations e.g. in CreateWorkspace.tsx render errors directly to HTML, instead of starting with plaintext first, and then rendering it.

[laushinka]

Closing because too stale. Picked up here.