fix: honor field defaults in nested Pydantic model function schemas

[NishchayMahor]

Summary

When automatic function calling generates a schema for a parameter that is a Pydantic model, sub-fields that have a default are incorrectly marked as required. This forces the model to supply values for parameters that should be optional.

import pydantic
from google.genai import types

class Foo(pydantic.BaseModel):
    a: int              # required
    b: int = 5          # has a default -> should be optional
    c: str = 'hello'    # has a default -> should be optional

def fn(foo: Foo): ...

decl = types.FunctionDeclaration.from_callable(client=client, callable=fn)
# decl.parameters.properties['foo'].required == ['a', 'b', 'c']   # BUG
# expected                                    == ['a']

Root cause

In _automatic_function_calling_util._parse_schema_from_parameter, the Pydantic-model branch builds each sub-field via inspect.Parameter(field_name, ..., annotation=field_info.annotation) but never passes field_info.default. The recursive call therefore sees no default, the sub-schema's default stays None, and _get_required_fields (not nullable and default is None) lists the field as required. Top-level parameters already work because their defaults flow through param.default; only nested-model fields were affected.

Fix

Forward each field's default into the sub-field inspect.Parameter, resolving default_factory via field_info.get_default(call_default_factory=True), and only when the field is not required. This leaves Optional-without-default fields (already handled via nullable) untouched and does not modify the shared _get_required_fields helper.

Verified across concrete defaults (b=5), factory defaults (d: list = Field(default_factory=list)), falsy defaults (f: int = 0), and Optional[int] without a default — only genuinely-required fields remain in required.

Testing

Added test_pydantic_model_with_default_fields to google/genai/tests/types/test_types.py (fails on main, passes with the fix). Existing schema/callable tests unchanged:

pytest google/genai/tests/types/test_types.py -k 'pydantic or default_value or built_in'   # 22 passed
pytest google/genai/tests/afc/ google/genai/tests/transformers/test_t_tool.py test_t_tools.py  # 122 passed

(2 pre-existing ReplayApiClient fixture errors in afc_thoughts are unrelated — they fail identically on clean main.)

This change was developed with AI assistance; I verified the root cause and behavior against the cited code paths, reviewed every line, and ran the tests above.

[NishchayMahor]

Rebased onto current main — the branch had drifted 100 commits behind, so I'd rather it be current before anyone spends review time on it than after. behind_by=0 now, clean rebase, no conflicts.

Worth flagging one thing I checked rather than assumed: 62d50d6 ("enable json schema in FunctionDeclaration parser") touched _automatic_function_calling_util.py, the same file this changes. The fix still applies and the behaviour is unchanged — google/genai/tests/types/test_types.py is 94 passed, 6 skipped, and with that file reverted to main the new test fails on its own:

FAILED google/genai/tests/types/test_types.py::test_pydantic_model_with_default_fields
1 failed, 93 passed

so it's still pinning the behaviour rather than passing incidentally.

The change itself is unchanged: a nested Pydantic model's fields with defaults were being emitted as required in the generated function schema. A model like

class Inner(BaseModel):
    a: str
    b: int = 3          # has a default

class Outer(BaseModel):
    inner: Inner

produced required: ["a", "b"] for Inner, so the model was told it must supply b even though the Python signature makes it optional. Top-level parameters already honoured their defaults; only the nested path didn't.

All checks are green and the CLA is signed. Is there anything you'd like changed, or a different reviewer I should tag? Happy to close it if the direction isn't wanted — I'd just rather that be a decision than a timeout.