feat: add CR id to plausible events

[sjaanus]

Added conflict count to CR metrics and CR id.

Something to think about:
There was idea that we can aggregate this data based on CR id, but CR id is just a number from 0 to x. So it will not be unique across instances.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
unleash-monorepo-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 30, 2024 8:23am

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
unleash-docs	⬜️ Ignored (Inspect)	Visit Preview		Jan 30, 2024 8:23am

[thomasheartman]

Regarding the uniqueness of CR ids across instances: this can be handled by using the instance's baseUriPath or its instanceId. I've made that change in dc0a198

[thomasheartman]

Regarding using base Uri path vs instance ID, I've discussed this in #6022, so I'll copy it in here. Happy to hear your thoughts:

I've set the Unleash baseUriPath as the preferred identifier. Because Plausible is only used on our hosted instance, it should always map to one of our customers (and the fallback should only be used if that's not available).

I'm a little hesitant about putting that data in the event because we don't really need that data. However, we could potentially use it to see if different clients have different usage patterns and encounter higher rates of conflicts.

I'd be happy to discuss this and move to preferring instanceId instead.

That said, I believe we can already do the correlation in plausible anyway due to the source of the events.