Handle DC Chat Feedback Submission

[kdid]

Summary

Handle DC chat feedback submission.

• Saves response to S3
  • Files can be overwritten in the case of a initial 👍 / 👎 followed by a more detailed response
• Sends notification/email to subscribers of topic

Steps to Test

• Fetch the branch and clean/build
• Deploy a development branch: Deploy Development Branch
• Go into the AWS SNS staging console and subscribe to the topic that was created, which should be named `{your-dev-env}-chat-feedback)
  • Look for the subscription confirmation in your email inbox and follow instuctions
• Visit the https://your-dev-branch-name.rdc-staging.library.northwestern.edu/api/v2/chat-feedback route (You can use the Postan POST chat feedback endpoint (screenshot below))
• You should receive validation errors for invalid JSON
• You should receive a success message/200 from the API when the form is submitted
• You should receive an email notifying you of the response (screenshot below)
• Find the {your-dev-env}-chat-feedback bucket and look for the response with a key of {sentiment}/{ref}.json

[mbklein]

Working great as written. I think we should backtrack very slightly and change the chat-endpoint and chat-feedback routes to chat/endpoint and chat/feedback just to keep things organized. They're both undocumented private API routes, so it wouldn't be a major-version breaking change, and I really like the idea of keeping the routing table better segmented by function. (This will also make it a lot easier to split things up when we get around to #4518.)

It'll require a small simultaneous front-end update, but I very much think it's worth it.

[mathewjordan]

Seems great to me. The one thing I saw is that it looks like you can send in the body without a context.ref, context.question, and/or a context.answer. Not sure if we want to bulletproof that more.

[kdid]

@mbklein and @mathewjordan - Addressed both of your comments. Thank you!

[mathewjordan]

🚀