feat: support static remote endpoint in ClientConfig (no SD)

[vtz]

Summary

• Add an optional remote_endpoint field to ClientConfig and forward it to UdpTransport / TcpTransport during SomeIpClient construction.
• This enables communication with SOME/IP servers that do not run Service Discovery (e.g. Zephyr-based MCU firmware with multicast TX disabled).
• Both transports already accepted the parameter — it just wasn't wired through the high-level config. The field defaults to None, preserving existing SD-based behavior.

Closes #13

Changes

src/opensomeip/client.py

• Added remote_endpoint: Endpoint | None = None field to ClientConfig
• Updated SomeIpClient.__init__ to forward config.remote_endpoint to both TcpTransport and UdpTransport constructors

tests/unit/test_client.py

• Added TestStaticRemoteEndpoint test class with 5 tests:
  • test_remote_endpoint_defaults_to_none — backward compatibility
  • test_udp_remote_endpoint_forwarded — UDP transport picks up the endpoint
  • test_tcp_remote_endpoint_forwarded — TCP transport picks up the endpoint
  • test_no_remote_endpoint_preserves_none — omitting the field preserves None
  • test_lifecycle_with_remote_endpoint — full start/stop cycle with static endpoint

Test plan

• All 271 unit tests pass
• 5 new tests cover the feature (both UDP and TCP paths, default/backward compat, lifecycle)
• CI green

Made with Cursor