chore: update test durations

[github-actions]

Automated weekly refresh of src/backend/tests/.test_durations,
used by pytest-split to balance the 5 backend CI test groups.
A stale file causes unbalanced groups and group timeouts
("fails at 99%"), so this PR should be merged promptly.

This PR was automatically created by the store_pytest_durations
workflow. Durations were measured per CI group with the same test
selection CI uses (-n auto, no api_key_required, no
unit/template).

If the Validate PR check is missing, edit the PR title (e.g.
re-save it unchanged) or push to the branch to trigger it — PRs
created with the default GITHUB_TOKEN don't fire
pull_request_target workflows.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.71%. Comparing base (33e7990) to head (09e924a).
⚠️ Report is 46 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14477      +/-   ##
==========================================
- Coverage   61.81%   61.71%   -0.10%     
==========================================
  Files        2452     2405      -47     
  Lines      240491   239031    -1460     
  Branches    34348    33875     -473     
==========================================
- Hits       148649   147517    -1132     
+ Misses      89992    89664     -328     
  Partials     1850     1850              

Flag	Coverage Δ
backend	68.97% <ø> (-0.11%)	⬇️
frontend	59.89% <ø> (-0.14%)	⬇️
lfx	61.10% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 142 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[erichare]

The generated duration artifact looks sound: the source workflow completed all five measurement groups, merged 11,809 tests, and the JSON contains only positive numeric timings. No review findings. Please still trigger the missing normal Validate PR workflow before merge, as the PR description notes.