Applies the changes from Dependabot PR #595 onto dev so they reach the dev branch ahead of the upstream PR (which targets main).

Refs: ADO #44960

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Applies the changes from Dependabot PR #596 onto dev so they reach the dev branch ahead of the upstream PR (which targets main).

Refs: ADO #44960

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…uv.lock

Applies the changes from Dependabot PR #597 onto dev so they reach the dev branch ahead of the upstream PR (which targets main).

Refs: ADO #44960

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Regenerated uv.lock after merging dev to incorporate both
dependabot upgrades and agent-framework 1.3.0 changes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

chore(deps): bring dependabot upgrades (#589, #595, #596, #597) onto dev (AB#44960)

…ial in python application.

…ores

Root cause: When the evaluate step couldn't compute any per-field confidence (e.g.
logprobs unavailable on reasoning models like gpt-5/o1/o3, or image-only flow with
no Content Understanding signal), save_handler emitted entity_score=0.0,
schema_score=0.0. These `0.0`s flowed through Cosmos -> API -> UI and rendered as
`0%` (red), indistinguishable from a genuine zero confidence.

Fix: Treat `total_evaluated_fields_count == 0` (or no comparison items) as
*unavailable* and propagate `None` through the ContentProcessor, ContentProcessorAPI
and ContentProcessorWorkflow models. The frontend percentage cell renderer now shows
`N/A` for null/undefined and `0%` only for a genuine numeric zero.

Files changed:
- ContentProcessor: save_handler.py (extracted _derive_aggregate_scores helper)
- ContentProcessor: content_process.py default scores -> None
- ContentProcessorAPI: ContentProcess + Content_Process default scores -> None
- ContentProcessorWorkflow: ContentProcessRecord + Content_Process default scores -> None
- ContentProcessorWorkflow: document_process_executor preserves None instead of
  coercing to 0.0
- ContentProcessorWeb: ProcessQueueGridTypes types scores nullable;
  ProcessQueueGrid passes undefined for null/undefined; CustomCellRender renders
  `N/A` when valueText is null/undefined and only `...` while still processing

Tests:
- New: ContentProcessor/tests/unit/pipeline/test_save_handler_scores.py (5 cases:
  valid scores, missing per-field signal, no comparison items, genuine zero,
  all-fields-above-threshold)
- Updated existing default-value tests in Workflow + src/tests to assert None
- Added tests for explicit zero preservation and Failed status -> None

Per feedback: Completed runs must always show a meaningful number; Failed runs and genuine zeros stay at 0%.

- save_handler._derive_aggregate_scores picks the best available signal: (1) probabilistic confidence when logprobs available; (2) structural completeness (filled fields / total) when no logprobs (reasoning models, image-only flow); (3) 0.0 when no extraction data at all.

- _is_filled_value heuristic: None/empty/whitespace count as not filled; descends into nested dicts/lists.

- Reverted models from Optional[float]=None back to default 0.0.

- Reverted frontend: no N/A path; renders 0% for null/missing scores.

- 15 new tests covering all 3 paths + _is_filled_value heuristic.

…ation

- F401: drop unused sync DefaultAzureCredential import in 3 credential util files (sync flow now raises RuntimeError; AsyncDefaultAzureCredential is still used).

- W293/E122: fix blank-line whitespace and continuation-line indentation in ContentProcessorWorkflow/src/utils/credential_util.py.

fix: Psl entity score