Feature/expand validation pydantic models 3d api

[javlor]

Extend 3D API Pydantic models with contract-compatible validation and optional fields:

• Tracker.tracker_rotation_id and tracker_system_id are optional
• Optimizer IDs enforce min_length=1, and optimizer configurations require fixed_voltage_from_inverter.
• IndexedObject3D.is_building defaults to False; name defaults to None.
• Module and terrain index/dimension fields now reject negative values.
• dc_ohmic_connector_resistance now enforces the API maximum of 10.

Additionally, fix an integration test for the About endpoint for the deprecated API v4.

[wholmgren]

agent discovered a new issue when trying to do a round trip test with the Matera data: TrackerSystem.east_west_gcr needs an alias to map onto the correct SF property. Recommend an integration test to ensure 3d pydantic models serialize into known working json.

east_west_gcr: float | None = Field(None, alias="eastWestGCR")

[wholmgren]

is this pre-existing block more strict than sf-core validation and should be removed? the new block and pydantic limits are sufficient?

[javlor]

This is a new validation check for API v7 (in the upcoming release) that originated from a couple of support issues recently. For those using the SDK, it gets validated it. Those using their own code, the validation service will catch it.

[javlor]

TrackerSystem.east_west_gcr needs an alias to map onto the correct SF property. Recommend an integration test to ensure 3d pydantic models serialize into known working json.

@wholmgren thanks for the comments. I have committed the changes for this issue. Explicit alias eastWestGCR helps match the API schema rather than the auto-generated camelCase alias eastWestGcr. I have added a test to check the serialization against the Matera tutorial files.