Remove misleading optional annotations from BeaconBooleanResponse fields

[Copilot]

The info and beacon_handovers fields in BeaconBooleanResponse were annotated as | None but used default_factory, meaning they're always initialized to empty collections and never None. This created misleading OpenAPI schemas and inconsistency with other response classes.

Changes:

• Removed | None from info field type annotation (now dict[str, Any])
• Removed | None from beacon_handovers field type annotation (now list[BeaconHandover])

Before:

info: dict[str, Any] | None = Field(default_factory=dict, ...)
beacon_handovers: list[BeaconHandover] | None = Field(default_factory=list, ...)

After:

info: dict[str, Any] = Field(default_factory=dict, ...)
beacon_handovers: list[BeaconHandover] = Field(default_factory=list, ...)

This aligns BeaconBooleanResponse with BeaconCountResponse, BeaconResultsetsResponse, and BeaconCollectionsResponse, which already follow this pattern.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

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:

• astral.sh
  • Triggering command: /usr/bin/curl curl -LsSf REDACTED (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)