Refactor feedback component

[chriswhong]

Overhauls the Feedback component, introducing a simpler UX:

• Prompts with a simple question "Was this [content type] helpful? Yes/No"
• Text entry is not required unless the user selects "Another reason" (users can easily submit simple feedback with 3 clicks)
• Text input is not shown until the user selects the categoryType.
• Segment events are simplified, there is one when the user first clicks Yes or No, and one when they submit.
• UI is simplified, there is no longer a close button, and no link to support. Internal state is simplified as well since we no longer need to track these items.

[AlexanderBelokon]

Awesome! Looks a lot less intimidating in terms of required text fields, and decisions on first steps also feel easier 🚀

One thing I do miss is the ability to go back if I clicked Yes instead of No or vice versa, but I guess this is mostly useful for testing, not so much for actual users

For reference, this is how it looked before:

[AlexanderBelokon]

Is relying on the order of buttons a safe practice? The usefulness of the comment above suggests that code itself is not specific enough to be understandable on its own.

Would finding the button by label text instead be more robust (and more similar to how a real person would look for it)?

[chriswhong]

Good point, I will fix this and push a commit.