fix: blanked out weekly file search results after record association

[plakkara-bc]

Description

PR Title

fix: clear Weekly File child search after associate/confirm to prevent stale matches

Summary

This PR fixes a workflow issue in CSA Weekly File Processing where the Child Search input retained the previous value after a record was associated and confirmed.
The stale search term could mislead users while processing the next unmatched record and increased risk of incorrect manual association.

Problem

In Weekly File Processing:

1. User filters for unmatched (CSA Match = No) and selects a record.
2. User searches for a child, clicks Associate, then Confirm.
3. Record is reprocessed and no longer visible under the unmatched filter.
4. On the next record, the previous child search text still appears in the Child Search input.

This created a significant operational risk for mismatches.

Changes Made

Updated child-search reset behavior in [backend? no frontend] Weekly File UI logic:

1. Clear Child Search state when selected record changes:

• Reset search input text (childSearchTerm)
• Reset selected search contact and search results/pagination state

2. Clear Child Search state after successful Confirm reprocess:

• After reprocess + data refresh, reset search input and all child-search context
• Ensures next matching task starts with a clean search box

Files Changed

• WeeklyFileProcessingTab.tsx

Behavior After Fix

After Associate + Confirm:

1. Child Search input is cleared.
2. Prior search results and selection are cleared.
3. Next worker activity starts with a clean state, reducing accidental associations.

Validation

1. Frontend build passed:

• npm run dev-build

2. Frontend tests passed:

• npm test -- --run (all green)

Risk

Low.
Changes are localized to Weekly File child-search state reset logic and do not modify API contracts or backend behavior.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Automated/Unit tests
• Manual tests (description below)
• No new tests are required

Checklist

• I have tested my changed locally
• The code builds and pass all tests, No warning
• I have made corresponding changes to the documentation

In Progress/Follow Up