Get a stream of gateway info (V4)

[kurotych]

Implement gateway_info_v4 with added owner and owner_changed_at

[Copilot]

Pull request overview

This PR introduces a V4 version of the gateway info streaming API to support tracking gateway ownership changes. The changes add two new fields (owner and owner_changed_at) to enable filtering and monitoring gateway ownership transfers.

Changes:

• Adds gateway_info_v4 message with owner tracking fields
• Adds gateway_info_stream_req_v4 request message with owner change timestamp filtering
• Adds gateway_info_stream_res_v4 response message and info_stream_v4 RPC method

---

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

[Copilot]

The instruction text differs from the corresponding field in gateway_info_stream_req_v3 (line 229-230). In v3, it says "Use 0 to fetch all gateways" while in v4 line 251 it says "Use 0 if you don't want to apply this filter". For consistency across API versions, consider using the same phrasing as v3.

Suggested change

	// Use 0 if you don't want to apply this filter
	// NOTE: It is recommended to use the highest `updated_at` field from
	// returned radios in the next subsequent requests.
	uint64 min_updated_at = 5;
	// The Unix epoch timestamp (in seconds).
	// Filters the response based on the last time gateway changed its location.
	// Use 0 if you don't want to apply this filter
	// Use 0 to fetch all gateways.
	// NOTE: It is recommended to use the highest `updated_at` field from
	// returned radios in the next subsequent requests.
	uint64 min_updated_at = 5;
	// The Unix epoch timestamp (in seconds).
	// Filters the response based on the last time gateway changed its location.
	// Use 0 to fetch all gateways.

[Copilot]

There is a discrepancy between the PR description and the code changes. The PR description states "Add owner and owner_changed_at to gateway_info_v3", but the code actually creates a new gateway_info_v4 message with these fields, leaving gateway_info_v3 unchanged. This is the correct approach for maintaining backward compatibility, but the PR description should be updated to reflect that this creates a V4 version rather than modifying V3.

[Copilot]

The comment format is inconsistent with the pattern used for other timestamp fields. The field 'owner_changed_at' should include "Unix epoch timestamp" at the beginning for consistency with other timestamp fields in this message (lines 138-144) and throughout the file. Consider changing to: "The Unix epoch timestamp (in seconds) when the owner was last changed"

Suggested change

	// The last time the owner was changed (in seconds)
	// The Unix epoch timestamp (in seconds) when the owner was last changed

[Copilot]

The comment format is inconsistent compared to the corresponding field descriptions in gateway_info_stream_req_v3. For consistency, lines 218-220 in v3 say "Returns all devices if empty" while v4 says "Use empty array if you don't want to apply this filter". While both are technically correct, it would be better to maintain consistency across versions unless there's a specific reason to change the wording.

Suggested change

	// Use empty array if you don't want to apply this filter
	// Returns all devices if empty