chore: migrate tests to protobuf Opaque API

[Copilot]

The tests folder was overlooked during the repository-wide migration to protobuf's Opaque API. Test files continued using direct struct field access, which is incompatible with the opaque message representation.

Changes

• Regenerated proto files with API_OPAQUE flag (Makefile already configured)
• Migrated message construction from struct literals to builder pattern
• Replaced direct field access with getter/setter methods

API Migration Pattern

// Before: Direct struct access
resp := &Response{
    Name: srv.name,
    Num:  req.Num,
}

// After: Builder pattern with getters
resp := Response_builder{
    Name: srv.name,
    Num:  req.GetNum(),
}.Build()

Affected Test Packages

• config - Configuration and node management
• correctable - Correctable quorum calls
• metadata - gRPC metadata handling
• oneway - Unicast/multicast operations
• ordering - Message ordering guarantees
• qf - Quorum function benchmarks
• tls - TLS authentication

All tests pass with the new API.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>chore: update tests to use protobuf's Opaque API</issue_title>
<issue_description>When we converted the repository to the opaque API, we forgot the different tests in the tests folder. We should fix that. This includes using the new protobuf _builder{Field: ...} instead of directly accessing struct fields, and invoking Build() at the end. In addition, all direct field accesses must use the field's Get and Set methods instead.

We need to run make in the tests folder to generate the new .pb.go files.

Here is an overview of the files to be updated in the tests folder:

$ tree
.
├── config
│   ├── config_gorums.pb.go
│   ├── config_test.go
│   ├── config.pb.go
│   └── config.proto
├── correctable
│   ├── correctable_gorums.pb.go
│   ├── correctable_test.go
│   ├── correctable.pb.go
│   └── correctable.proto
├── dummy
│   ├── dummy_gorums.pb.go
│   ├── dummy.pb.go
│   └── dummy.proto
├── Makefile
├── metadata
│   ├── metadata_gorums.pb.go
│   ├── metadata_test.go
│   ├── metadata.pb.go
│   └── metadata.proto
├── mock
│   ├── mock.pb.go
│   └── mock.proto
├── oneway
│   ├── oneway_gorums.pb.go
│   ├── oneway_test.go
│   ├── oneway.pb.go
│   └── oneway.proto
├── ordering
│   ├── order_gorums.pb.go
│   ├── order_test.go
│   ├── order.pb.go
│   └── order.proto
├── qf
│   ├── qf_gorums.pb.go
│   ├── qf_test.go
│   ├── qf.pb.go
│   ├── qf.proto
│   └── readme.md
├── tls
│   ├── cert.go
│   ├── tls_gorums.pb.go
│   ├── tls_test.go
│   ├── tls.pb.go
│   └── tls.proto
└── unresponsive
    ├── unreponsive_test.go
    ├── unresponsive_gorums.pb.go
    ├── unresponsive.pb.go
    └── unresponsive.proto

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes chore: update tests to use protobuf's Opaque API #237

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[deepsource-io]

Here's the code health analysis summary for commits e2dce59..fb5e27f. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Go	✅ Success	🎯 5 occurences resolved	View Check ↗
Shell	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.