Egress stream retry info

[milos-lk]

When egress uses RTMP streams as outputs - it could happen that a remote RTMP server (or something in between) closes connection. Egress is auto retrying already started recordings but frequent retries could cause multiple video files being recorded on the remote (vendor side - we had a specific case of too many small youtube videos being created)

The suggested protocol update would enable us to communicate when this happens so that publishing side could take some action if needed.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 945c4e2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "github.com/livekit/protocol" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[biglittlebigben]

How is this communicated to the client? Through a webhook?

[milos-lk]

How is this communicated to the client? Through a webhook?

Yes - that's correct - through web hook

[anunaym14]

maybe timestamp for last_retry_at and uint for retries?

[milos-lk]

thought about it - chose int64 for retry_at to be consistent with started_at and ended_at.
retries could be uint though

[milos-lk]

Hm - there is a conflict in the autogenerated code - the cleanest way to resolve this would be opening a new PR (not wise to fiddle with autogenerated code)