feat: feedback component submits to feedback table + tidy ups

[jamdelion]

In this PR:

Improvements from comments on previous PR:

• Fixed more information link not appearing as expect on public component
• Swapped RichTextInput for TextInput component in public view
• Restyled disclaimer using shared component
• Renamed placeholders file given will be used in templates, and made the object typeable.

Also:

• Fixed styling of face boxes uppercase text.
• Hook into existing feedback API (added 'feedback score' column to table)
• Also add _feedback to breadcrumbs on submit

How to test 🧪

• Turn on the feature flag with `window.featureFlags.toggle("FEEDBACK_COMPONENT").
• Try to add a Feedback component to a flow, publish it etc!

🎟️ Trello ticket: https://trello.com/c/jEOLoubW/3034-can-we-introduce-in-house-end-of-service-feedback

Todo:

• e2e testing
• Add feedback score to feedback log table, and add new feedback type (currently renders as default 'inaccuracy')
• validation and error handling, with testing
• use the _feedback key in metabase (add to allow_lists)
• make sure component works on 'back' - previouslySubmittedProps

[github-actions]

Removed vultr server and associated DNS entries

[github-actions]

🤖 Hasura Change Summary compared a subset of table metadata including permissions:

Updated Tables (1)

• public.feedback permissions:

  	insert	select	update	delete
  public	➕/➖

  1 added column permissions

  	insert	select	update
  public	➕ feedback_score

[DafyddLlyr]

Great stuff - working as expected 👍

Code is clear and well structured, easy to review and follow along.

One thing for a follow up PR is to make sure that the component works on "back" - have a look at how the previouslySubmittedData prop is used in other components.

A few comments below - let me know if you want to talk anything through.

[DafyddLlyr]

Please see previous comment - maybe an integer column with a CHECK constraint (e.g. 1-5) is a good option here.

[jamdelion]

One thing I'm not sure of - can I delete some of these migrations to make the PR cleaner? Or is my back and forth on this immortalised forever more? 😅

[jessicamcinchak]

Yes! Can manually combine migrations into a single up.sql (note you'll want to destroy Vultr before pushing commit so it rebuilds from scratch to test) or there's a Hasura CLI squash command (I find this command finicky and usually go the manual route tbh!)

[jessicamcinchak]

Changes & previous feedback all look good here - happy to approve to not block progressing !

Dismissing "requested changes" while Daf is out sick!