Replay: Make sure the Breadcrumbs component displays new 'SDK start' crumb

[bruno-garcia]

Problem Statement

When the SDK is used on a page that posts back to the same URL, we don't capture any breadcrumbs (e.g; navigation).
That information in events is required by the Replay player so we can know what URLs we're at, and properly present them over the player.

Solution Brainstorm

Once getsentry/sentry-javascript#7259 is completed, look for those new breadcrumbs to feed into today we rely on navigation breadcrumbs.

[ryan953]

@bruno-garcia This is missing a link to the mentioned issue

[billyvg]

Shouldn't this belong in sentry-javascript?

From Slack:

I think this is when we start a new session from an existing page (e.g. due to session idle timeout)

In this case, we shouldn't add a navigation breadcrumb, but it might be good to indicate somehow that a session was expired and a new one was started. We also need to ensure that a URL is included in the replay event.

[bruno-garcia]

I created this at the time: getsentry/sentry-javascript#6928
But that was closed through getsentry/sentry-javascript#7029 but I'm not sure that'll help achieve what we this issue tracks.

Created now: getsentry/sentry-javascript#7259 (updated description)

[billyvg]

Do we have an example replay of this happening? Wondering how you're determining it's a post back that is causing this.

[bruno-garcia]

Sadly I don't. This came up from a PHP app.

Maybe @cleptric has experienced this with his dogfooding like gibpotato? @cleptric problem here is that when the customer loaded a replay it didn't have the right URL on top of the player. IIRC there was no JS playing a role, it was just posting back for any interaction and rendering again on the server.

I just lowered this to p2 since it hasn't come up again since then