Expose Nexus Endpoint on Nexus Info

[Quinn-With-Two-Ns]

What was changed

Expose the Nexus Endpoint to the SDK.

Why?

So the handler knows what endpoint the request originally came from for visibility and per endpoint encryption

Checklist

1. Closes

2. How was this tested:

3. Any docs updates needed?

closes: #2836

---

Note

Medium Risk
Adds a new method to the public NexusOperationInfo interface and threads a new endpoint value through Nexus task handling; this can be source-breaking for any external implementations and depends on server-provided data.

Overview
Exposes the Nexus request’s original endpoint name to operation handlers by extending NexusOperationInfo with getEndpoint().

Threads the endpoint from the incoming Nexus Request into InternalNexusOperationContext/NexusInfoImpl and through interceptor initialization so Nexus.getOperationContext().getInfo().getEndpoint() returns it. Updates the test server to populate Request.endpoint in poll responses and adjusts NexusOperationInfoTest expectations accordingly.

^{Reviewed by Cursor Bugbot for commit d660166. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d66016626e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".