Separate running/latest build from viewed stories

[tmeasday]

Implement behaviour for "next" builds discussed in linear, namely:

1. Don't switch the story we are looking until you click a button in the eyebrow
2. But if you change story, switch to a "next" latest build as soon as it is available.
3. Additionally, always use the next build to drive the sidebar.

Relies on chromaui/chromatic-cli#810 and telescoping on #68

📦 Published PR as canary version: 0.0.51--canary.69.503ff0c.0

✨ Test out this PR locally via:

npm install @chromaui/addon-visual-tests@0.0.51--canary.69.503ff0c.0
# or 
yarn add @chromaui/addon-visual-tests@0.0.51--canary.69.503ff0c.0

[linear]

AP-3544 Implement "build of out date" behaviour

As discussed in Slack: https://chromaticqa.slack.com/archives/C051TQR6QLC/p1692354384352659

1. When a new (local) build is running, show a eyebrow UI for the progress (AP-3559)
2. When it is complete, continue to show the old build, but prompt the user to switch
3. When they switch or change stories, show the new build from now on.
4. When you change branch/commit, if there is a newer CI build available, behaviour similarly as to 2&3
5. Alert users when there is a new build available on a newer commit on the current branch.

Some details still being thrashed out. The details of the eyebrow and 5. are probably large enough to deserve their own tickets.

Discussion here: https://www.notion.so/chromatic-ui/Persisting-information-in-the-addon-20f4b982692b40d09e4211635581e62b?pvs=4

[ghengeveld]

I think we're going to refactor this a bit more later on (mostly to pull apart VisualTests.tsx), but this is a step in the right direction 👍