fix(json-type): add support for JSON columns in the service dashboard

[Perseus]

Fixes #1023

• Adds a useJsonColumns hook which returns the names of all JSON columns in a specific table
• Modifies the syntax used to access attributes in the traces table based on the type of the column
• Changes some coalesce(nullIf(...)) queries to access the fields directly due to ClickHouse not supporting NULLIF() on dynamic columns

[vercel]

@Perseus is attempting to deploy a commit to the HyperDX Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: bfff2fe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Perseus]

@wrn14897 @knudtty
Thanks for the review!

I've made a function to generalize the creation of coalesced queries based on both of your comments; it feels a little awkward since its building the queries manually and I've tried to keep the queries well-indented to make troubleshooting easier without adding significant amounts of whitespace, but it would be significantly easier if there was a standardized query builder (or I could also write a query builder specifically for this use-case if that sounds better).

I've addressed the remaining comments as well.