test: add browser_session_expires_at to the connection fixture

[Chen-ROE]

Unblocks #83. Release 1-1-0 adds browser_session_expires_at as a read-only, nullable field on Connection. The generated Connection.from_dict pops it with no default, so the hand-written fixture in tests/unit/test_connections_wrapper_transport.py fails three tests with KeyError.

Adding the key here rather than on the #83 branch because the roe-main fan-out resets release-sdk-python-1-1-0 on every push to release-1-1-0, so a fix there is discarded by the next cherry-pick.

Verified locally on main (62 passed) and on the #83 branch with the same change (62 passed). On main the current generated model routes the extra key to additional_properties, so nothing changes until #83 regenerates on top of this.

After merge, re-run the roe-main release workflow on release-1-1-0 (or push any commit to it) so #83 is rebuilt green.

🤖 Generated with Claude Code

[greptile-apps]

Confidence Score: 5/5

[Low risk] Adds a field to a test fixture.

This fixture-only change appears safe to merge.

What we checked:

• Extra field breaks existing tests: The current parser keeps extra fields in additional_properties. The tests check only the returned ID and independently built request bodies.

Summary

Adds "browser_session_expires_at": None to the shared connection response fixture in preparation for the generated model change.

• The current parser accepts the extra field.
• Existing request-body assertions remain unchanged.
• No actionable issues found. Tests were not run during this review.

_{Reviews (1) · Last reviewed commit: "test: add browser_session_expires_at to ..." · Reviewed by Greptile}