Push events from the client instead of polling for them

[jerelmiller]

Reintroduces the __actionHookForDevtools hook which allows us to push updates from the client to the devtools. This removes the need for polling from the devtools for updates continuously.

As a result, the polling code is (mostly) gone except for the handling of one edge case where queries kicked off right after the client is registered are not reported via the action hook. We will poll for a brief time until we know the client starts pushing data again or it disconnects.

This change has the benefit that changes from the client are reflected immediately in the devtools UI rather than waiting for the next tick of the poll interval so it feels a bit snappier.

To test this, try a few different situations:

• Navigating around the app to ensure the listed queries change
• Reload the page to ensure the data is shown in the devtools after refresh
• Destroy/recreate the client

[relativeci]

#441 Bundle Size — 1.26MiB (~-0.01%).

45933c6(current) vs 0a5a26f main#431(baseline)

Warning

Bundle contains 12 duplicate packages – View duplicate packages

Bundle metrics   2 changes 1 improvement

	Current #441	Baseline #431
Initial JS	1.22MiB(~-0.01%)	1.22MiB
Initial CSS	0B	0B
Cache Invalidation	3.37%	0%
Chunks	5	5
Assets	12	12
Modules	940	940
Duplicate Modules	45	45
Duplicate Code	3.82%	3.82%
Packages	160	160
Duplicate Packages	9	9

Bundle size by type   1 change 1 improvement

	Current #441	Baseline #431
JS	1.22MiB (~-0.01%)	1.22MiB
IMG	35.85KiB	35.85KiB
HTML	810B	810B
Other	778B	778B

---

Bundle analysis report Branch jerel/push-client-events Project dashboard

[jerelmiller]

This bit of code was kept around from some legacy behavior (pre-actor/rpc days) where it would keep around the old data on screen until the another client connected, then it would reset it and use the new data.

This actually caused a bug in the change from this PR due to the sequence of events where we'd initialize the panel with data already in the client, but because this was cleared on the connected event, it would show no data.

I always thought this behavior was a bit strange anyways since it sorta made it seem like the devtools were still connected in some way to the old client. Instead, this will now reset all data if the client is no longer connected.

[phryneas]

Read the code and tested it - this is amazing! :)

[jerelmiller]

Going to push out the other two changes, then will get to this next week. Spacing them will ensure the other release doesn't break anything.