chore(tests): drive RPC over goridge net/rpc again

[rustatian]

Part of the org-wide Connect-RPC revert: test helpers drive the RPC surface over goridge net/rpc again, keeping the current api-go message set. Plugin deps in tests/go.mod are pinned to the revert branches (pseudo-versions to be replaced by tags). No changes outside tests/.

[Copilot]

Pull request overview

This PR updates the test suite to drive the Jobs RPC surface over the goridge net/rpc transport again (as part of the Connect-RPC revert), while keeping the current api-go message types. It also updates test-only Go module dependencies to pinned pseudo-versions on revert branches.

Changes:

• Replaced Connect client usage in tests with goridge net/rpc client calls (client.Call("jobs.*", ...)).
• Updated tests/helpers to create a goridge net/rpc client and switched helper RPC invocations accordingly.
• Updated tests/go.mod / tests/go.sum to drop Connect deps and pin RR plugin deps to revert-branch pseudo-versions.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File	Description
tests/jobs_beanstalk_test.go	Switches Declare helper invocation from Connect request to goridge net/rpc call.
tests/helpers/helpers.go	Replaces Connect Jobs client with goridge net/rpc client and updates helper RPC calls.
tests/go.mod	Removes Connect dependencies and pins RoadRunner plugin dependencies to revert-branch pseudo-versions.
tests/go.sum	Updates checksums consistent with dropping Connect/grpc deps and using pinned pseudo-versions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Warning

Review limit reached

@rustatian, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 169a8330-2140-4b8b-bf86-3bb7f6cf29a2

📥 Commits

Reviewing files that changed from the base of the PR and between 9426220 and fe40c7e.

⛔ Files ignored due to path filters (1)

• tests/go.sum is excluded by !**/*.sum

📒 Files selected for processing (3)

• tests/go.mod
• tests/helpers/helpers.go
• tests/jobs_beanstalk_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch revert/connectrpc

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}