feat(web-console): add materialized views support

[emrberk]

• Optimizes table listing using GroupedVirtuoso from react-virtuoso. Reduces render time in case we have 1000s of tables / mat. views.
• Adds SQL grammar support for materialized views.
• Materialized views shows the base table, and copying schema invokes show create materialized view... instead of show create table.
• Resume WAL button, in case of suspension, is moved to right-click context menu.
• Copy Schema action is available in the context menu.
• Fixes hide/show tables wording. We were showing "hide" even when it was hidden. Changes "tables" wording to "data sources" (highly subject to a discussion).
• Adds icons for different column types.
• Moves column type text to the left, changes the color.
• Replaces react-contextmenu with @radix-ui/react-context-menu due to bugs.
• Adds e2e tests for UI changes.

[goodroot]

Congrats on first PR 😀 - I appreciate the approach & fearlessness.

A couple broad questions, a some comments, and a few visual/functional things.

🫡 Solid push.

---

It is not clear how to "use" the materialized view.

We can see them and copy the query. But there isn't any interactivity beyond that.

What is the goal of the current view?

Can we "help" more?

• Link out to docs somewhere if there's no view? ie. better zero-state?

• Instead of a copy, perhaps create a tab & launch the query on click?

• If "materialized view" tab is active, execute query when appropriate?

Maybe beyond the scope of our first increment, and we might not have answers yet.

That's cool. 😃 But let's figure out where we're going.

---

"Invalid" states are missing.

There are conditions which can invalidate a mat view:

• Schema changes to the base table
• With deduplication, views must use same grouping keys as the base table's UPSERT KEYS
• More

During these states, the view needs a REFRESH. Do we guide through these cases?

More fatally, if the base table is dropped, there's no feedback.

For this, base table row is a potential space for warning and repair guidance:

---

The Table & Materialized view sections match base BG colour.

It seems off to me. Can we delineate them in a stylish way?

Maybe so tables & mat view look as "children" within data sources section?

---

Symmetry of the toggleable data sources button broke with filter change:

Before, it balanced with table view contents:

[emrberk]

Can we delineate them in a stylish way?
Maybe so tables & mat view look as "children" within data sources section?

@goodroot please take a look at this one:

The hierarchy seems more visible this time.

[emrberk]

Hey @goodroot, I updated the PR with the design we agreed on the discussion.

still wip

[goodroot]

Solid work - the tree view feels fast and the ux is clean.

In another iteration, it'd be worthwhile to make the mat view section useful.

Right now, it's informational.

But "open query in tab" or something would go a long way.

I will have to step away for some time.

So, LGTM from here. 👍