Telemetry: Add precedingUpgrade data to dev/build/error events

[shilman]

Issue:

What I did

If it's the first dev/build/error run after an upgrade, record a reference to that upgrade. This will allow us to track failures more easily and improve our upgrade heuristics.

This PR is a replacement for #20084 and #20099. In addition to improving the logic to avoid double-counting, it also adds a mutex around the cache saving.

The mutex code needs tests in a second iteration. But the error showed up in CI before, so for now we're going to use that as a sanity check.

How to test

In a test project, where sb is aliased to your local version:

STORYBOOK_TELEMETRY_DEBUG=true sb upgrade --prerelease
STORYBOOK_TELEMETRY_DEBUG=true sb dev    
STORYBOOK_TELEMETRY_DEBUG=true sb dev

The first dev event should contain extra data like

    "precedingUpgrade": {
      "timestamp": 1670159585083,
      "eventType": "upgrade",
      "eventId": "Y54r_tWjm9BFrYKGRHQt8",
      "sessionId": "U9A7qs-aiuDQt6tO4z_rv"
    },

The second should have none

To test an error, add one to your .storybook/main.js