fix(insights): Fall back to dataNodeLogic results and add dashboard concurrency

[webjunkie]

Problem

If an insight on a dashboard has an error/timeout, we can fall back to dataNodeLogic which will use another endpoint and possibly an async query to get the results after all.

Changes

• fix again conditions: the propsChanged function gets more hairy. We do want the dataNodeLogic to load results if there aren't yet any, but we need to make it stop when the cachedResults coming from other logics are enough
• add concurrency handling: load 2 insights at once

Does this work well for both Cloud and self-hosted?

n/a

How did you test this code?

• clicked through various dashboards
• let's see what tests say

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 2)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[webjunkie]

Wut

[posthog-bot]

📸 UI snapshots have been updated

2 snapshot changes in total. 0 added, 2 modified, 0 deleted:

• chromium: 0 added, 2 modified, 0 deleted (diff for shard 1)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[posthog-bot]

📸 UI snapshots have been updated

2 snapshot changes in total. 0 added, 2 modified, 0 deleted:

• chromium: 0 added, 2 modified, 0 deleted (diff for shard 1)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[github-actions]

Size Change: 0 B

Total Size: 1.05 MB

ℹ️ View Unchanged

Filename	Size
frontend/dist/toolbar.js	1.05 MB

_{compressed-size-action}

[mariusandra]

It would probably be safer to do this in two PRs, but let's try.