Adding SDK Ergonomics Query link

[Evanthx]

The one thing to note is that there was some duplication around link converters and still is. I would like to fix that separately, and have created an epic to check over the link converters for each SDK which I am planning on doing in the next sprint.
https://temporalio.atlassian.net/browse/NEXUS-578

The proto bump brings in the link field.

[Quinn-With-Two-Ns]

duplication around link converters and still is

What duplication? I am not aware of any except for what we had in the Go SDK/Server

[Quinn-With-Two-Ns]

Other then the tests the actual SDK changes LGTM

[Quinn-With-Two-Ns]

FWIW I also ran a Codex review and it only had one finding

  - Medium — nexusLinkToWorkflowLink (https://github.com/temporalio/sdk-java/blob/accc671abce2496605da46ec28c1966613e8b220/temporal-sdk/src/main/java/io/temporal/internal/common/LinkConverter.java#L232-L238) uses form-style URLDecoder for path
    segments, turning literal + into a space. A Go-produced workflow ID a+b would therefore become a b, potentially pointing to the wrong execution. The new test currently codifies this bug
    (https://github.com/temporalio/sdk-java/blob/accc671abce2496605da46ec28c1966613e8b220/temporal-sdk/src/test/java/io/temporal/internal/common/LinkConverterTest.java#L855-L883). Use a path-segment percent decoder that preserves +, then invert
    that assertion. The Go reference converter uses PathEscape/PathUnescape (https://github.com/temporalio/api-go/blob/85042fb4769bb46c3ed1addac9de526af51f4d83/temporalnexus/link_converter.go#L336-L405).