Add max round trip latency

[1egoman]

Adds a new max_round_trip_latency field to PerformRpcData, adding similar behavior as was added to the corresponding swift and android pull requests.

Note that this is a breaking api change. Per @ladvoc's guidance, this was deemed to be ok because there isn't really a great way to add this new field to the PerformRpcData struct in a backwards compatible way.

Given this is a breaking change, I opted to break it in a way where if we have to add more fields in here in the future, it could be done in a non breaking way by making PerformRpcData use a builder pattern. That results in something that looks like:

let output = caller_room.local_participant().perform_rpc(
    PerformRpcData::new("identity", "method") // <-- New builder
        .with_payload("payload")
        .with_response_timeout(Duration::from_secs(5))
).await?;

[github-actions]

Changeset

The following package versions will be affected by this PR:

Package	Bump
livekit	minor
livekit-ffi	patch

[1egoman]

@ladvoc Before merging, any preference on with_payload(payload: impl Into<String>) versus with_payload(payload: impl ToString)?

The benefit of the latter is something like a serde value just works (ie, with_payload(json!({ hello: "world" }))), but the con is there's an extra copy involved.

[ladvoc]

The benefit of the latter is something like a serde value just works (ie, with_payload(json!({ hello: "world" }))), but the con is there's an extra copy involved.

I would go with impl Into<String> to avoid the extra copy and to maintain consistency with other APIs.