Integ 231 improve error handling within analytics app component

[lilbitner]

Purpose

This PR accomplishes the following:

1. Adds more robust error handling for the common errors when rendering the GA4 app in the Sidebar. ⛔
2. Fixes some small UI issues. ✨

Approach

Error handling:

I added a component here called the ErrorDisplay component that is rendered in place of the Chart itself when an error is thrown. This component handles the anticipated two most common errors, providing an invalid argument somehow which is unlikely (invalid propertyId.), or a disabled Data api error. If the error does not belong to one of these error types, then the provided error message is displayed. I added a comment on this code to perhaps adjust the logic to display an actionable default error message if the error is not properly identified by the frontend, instead of the "mystery" error message.

Example error message for invalid arguments:

Small UI fixes:

Note content not wrapping appropriately:

Before:

After:

Outline of Date range Select menu cut-off on right side:

Before:

After:

[whitelisab]

Looks great to me! Just added a couple small comments/questions!

[ryunsong-contentful]

Everything looked good as far as the stuff you mentioned UI/Error Handling and overall great work on much needed fixes!

Two things however

1. Storing the React component in state.
2. I found two unhandled error cases (which produces the screenshots below)
   a. One where you kill the lambda (ie no server/server error/500s)
   b. Invalid service key

---

Now this PR only says to improve the error handling. So if this is just a foundation PR for handling Errors, I'm cool with you creating a ticket and handling those fixes separately as your next task (I'm also fine with you fixing them in this PR).
The second point will be a relatively annoying refactor for you but I think it'll prevent a lot of headaches down the road and is worth fixing in this PR.