test(recordings): Treat initial player state as aria-busy

[Twixes]

Changes

From the naming of the READY member of SessionPlayerState, I thought this meant the player is ready – but no, that means it's in its initial state and being made ready at that stage.
Clarifying that into INIT and treating that state as a busy state should prevent flakiness of player UI snapshots, such as this: #17532 (comment)

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 1)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 1)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[benjackwhite]

🤔 I don't follow. The "Ready" state means "I have loaded my metadata and am ready to play but am not actively playing yet" - for example when it is in a notebook, we dont have autoplay on.

aria-busy is meant for loading states, which the "Ready" or "init" state is not.

[Twixes]

Hmm, fair, this assumed that autoplay is always on. Unfortunately also clearly this does not solve the flakiness problem, because this commit is exactly the thing that shouldn't happen 😅 Can you add the correct waitForSelector to recordings stories in a separate PR to prevent this from happening? 🙏