fix duplicate session recording creation

[fspmarshall]

Fixes an issue where duplicate session recordings could end up being created in teleport clusters experiencing interruptions during session recording upload from agent to auth. In all observed cases of this bug, it seems to have been produced by a combination of two factors:

• Agents weren't syncing their upload status to disk until after the first successful event submission, increasing the likelihood that agents would create orphaned uploads.
• Auth servers were uploading slices even when empty, increasing the likelihood of orphaned upload attempts resulting in session recordings being created.

Both of the above cases are addressed in this PR. Note, however, that this PR does not address correctly selecting the non-empty upload for existing recordings affected by this issue. That will have to be the subject of future work (see #45917). It also doesn't prevent duplicates due to loss of agent-side cursor state or timeout of a partially completed upload attempt (e.g. due to an agent being offline for a prolonged period of tim), both of which were previously known "expected" cases in which duplicate recordings could be produced.

This issue is loosely related to #45786 as the two issues tend to happen together since they are both triggered when the session recording system is under extremely high load.

changelog: fixed an issue that could result in duplicate session recordings being created

[rosstimothy]

/excludeflake *

[public-teleport-github-review-bot]

@fspmarshall See the table below for backport results.

Branch	Result
branch/v14	Create PR
branch/v15	Create PR
branch/v16	Create PR