relayer: update client bindings to 0xsequence/relayer@ab4093e

[patrislav]

Summary

Regenerate relayer/proto/relayer.gen.go and lib/mock/relayer.mock.go from 0xsequence/relayer@master (0b3c169 → ab4093e).

Motivating addition — GetMetaTxnStatus(ctx, metaTxID) (ETHTxnStatus, bool, *MetaTxnReceipt, error), the non-blocking counterpart to GetMetaTxnReceipt (which blocks ~25s). It returns the live ETHTxnStatus — so QUEUED/SENT/MINED/DROPPED are now observable, not just terminal receipts — with receipt set iff the status is SUCCEEDED, FAILED or PARTIALLY_FAILED.

Also carried in by the bump:

• webhookUrl / webhookAuthToken params on Add/UpdateGasSponsor and the ecosystem variants, plus the matching GasSponsor fields.
• includeNonSponsored param on GetMetaTransactions.

No new wrapper helpers: GetMetaTxnStatus is reachable via the embedded proto.RelayerClient. A non-blocking method on the sequence.Relayer interface would need a new return type (MetaTxnStatus can't express QUEUED/SENT/MINED/DROPPED) and a second implementation in LocalRelayer, which has no relayer client — left out until something needs it.

Test Plan

• go build ./... passes
• go vet ./relayer/... ./lib/mock/... clean
• go test ./relayer/... ./lib/mock/... passes
• go generate ./lib/mock is idempotent
• var _ sequence.Relayer assertions for Client and LocalRelayer still compile
• Consumed downstream by waas, which now polls GetMetaTxnStatus instead of GetMetaTxnReceipt

Follow-up

waitMetaTxnReceipt (relayer/relayer.go:406) hot-spins with a bare continue and no backoff while the receipt is nil. GetMetaTxnStatus is the right primitive to fix that, but it changes wait-loop behavior — left for a separate change to keep this bump behavior-neutral.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-09T10:38:57.367229Z	6f8428f	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.