Poll for Git repository hash and set isOutdated when it changes

[ghengeveld]

This generates a single hash representing the current state of the Git repository, and sends a channel event whenever the hash changes. The panel sets isOutdated: true whenever it receives the event.

There are a bunch more improvements on this PR, including a fix to how the Tool and Panel synchronize state, how/when the "run tests" button shows a spinner/is disabled, a fix to prevent the UI from flickering while polling, and a tweak to never stop polling for build/tests.

📦 Published PR as canary version: 0.0.22--canary.31.f264f7e.0

✨ Test out this PR locally via:

npm install @chromaui/addon-visual-tests@0.0.22--canary.31.f264f7e.0
# or 
yarn add @chromaui/addon-visual-tests@0.0.22--canary.31.f264f7e.0

[linear]

AP-3369 Add concept of outdated builds

• Store a "git changes" hash as well as the commit hash on the build (ideally in the index, but it could be locally).
  • The CLI could understand the concept of a "uncommitted builds" also.
• Poll git for the current commit hash + changes hash (we also need to poll for branch for AP-3366 eventually)
• Consider snapshots out of date if the two don't match.

To get a hash of staged+unstaged+untracked changes:

(
 git diff --name-only --diff-filter=d --cached; 
 git diff --name-only --diff-filter=d; 
 git ls-files --others --exclude-standard
) | git hash-object --stdin-paths | git hash-object --stdin

This seems to be the only way to get a full hash of all these types of changes, whilst excluding any deleted files (which would cause an error because they can't be hashed).

[tmeasday]

Looking good.

Can we move the gitStateHash code to the CLI and pull it from there? I already do that (for the other git info) in this PR: https://github.com/chromaui/addon-visual-tests/pull/26/files

[tmeasday]

Looks great! This looks like it includes some fixes for other issues too, make sure you close them too if so!