feat(insights): Use GlobalDrawer instead of details panel II

[gggritso]

Attempt #2. The previous PR had to be reverted because I didn't account for URL behaviour.

This PR is very similar, but now opening and closing the span samples drawer is done in a special hook that watches for the required URL parameters.

---

Closes #81273

Replaces all Insights side panels with new GlobalDrawer implementations that match the drawers in Issues. The visual changes are minimal

1. Slightly different animations
2. A "Close" button on the top left of the drawer
3. Scroll bars on the left of the drawer
4. Tighter padding
5. Panel doesn't re-animate as often on clicking another transaction

There are small feature changes!

• no more docking bottom or right. Docking is to the right only
• panels now have closing animations

Before:

After:

Code Changes

GlobalDrawer is invoked with a hook, rather than rendered inline. So, I had to make some changes.

Before:

• rendering panels mostly unconditionally like <CacheSamplesPanel />
• each sample panel checks the URL to see if it's supposed to be open
• if open, renders itself, otherwise stays invisible
• on close, updates the URL, which re-renders and hides

This is problematic for a bunch of reasons:

1. When components can decide to not render themselves, the code flow is confusing. Parents should generally decide when to render children
2. When a component is rendered but hidden, it runs its side effects. This means that in our case, network requests were sometimes going out, even though the panel isn't visible

After:

• the panel is rendered using a useEffect, the effect detects a necessary URL parameter or state, and open the panel if necessary. All conditions that the panel used to check for itself are passed as parameters to the hooks
• the panel is rendered straight, it doesn't have any conditionals to check if it's supposed to be open
• on close, the panel hides itself, and tells the parent to update the URL or state as necessary

This is tidier, avoids component side-effects, and preserves closing animations! Plus, this means I can re-use a header component, make the analytics tracking consistent, etc.

---

This only leaves a small handful of users of DetailPanel, mostly in the trace view.