Add connection_endpoint to PrivateLink response

[shreyasj-livekit]

Summary

• add connection_endpoint to livekit.PrivateLink
• clarify endpoint is the customer-provided endpoint identifier
• regenerate cloud agent protobuf/twirp outputs

Why

Private link responses need to expose both:

• customer endpoint identifier (endpoint)
• LiveKit DNS endpoint for agent code (connection_endpoint)

Notes

This is intended to be consumed by dependent updates in:

• livekit/cloud-agents
• livekit/livekit-cli

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4513cd5

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.