[FLINK-40530][runtime-web] Isolate per-entry failures in job overview aggregation

[argoyal2212]

What is the purpose of the change

HistoryServerArchiveFetcher#updateJobOverview() aggregates every archived job's overview JSON into one combined /jobs/overview response. Today a single malformed or version-incompatible archive throws during aggregation and aborts the whole update, silently returning empty/stale overview data for every job, not just the offending one. This PR adds per-entry isolation so one bad archive can no longer take down the entire job listing.

Brief change log

• updateJobOverview() now catches and skips a single archive's parse failure instead of letting it abort the whole aggregation
• Logs a warning per skipped entry plus a summary count, instead of one opaque top-level error
• Guards against overwriting a previously-good combined overview if every entry fails on a given refresh cycle

Verifying this change

This change added tests and can be verified as follows:

• Added testUpdateJobOverviewSkipsMalformedEntryInsteadOfFailingEverything, which injects one malformed per-job overview entry alongside a valid one and asserts the valid job is still listed
• Added testUpdateJobOverviewDoesNotWipeGoodOverviewWhenAllEntriesAreMalformed, which corrupts the only entry and asserts the previously written combined overview is preserved rather than replaced with an empty one

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: GitHub Copilot CLI

[argoyal2212]

@zentol @gaborgsomogyi @dmvk Can I please get some help on this PR review. Thanks!

[flinkbot]

CI report:

• 8850b06 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[Jackeyzhe]

Thanks for this PR, LGTM

[spuru9]

LGTM

Optional: As this will have effect on the UI, could help with a comparison. Can skip if not easy to reproduce the instance.

[argoyal2212]

LGTM

Optional: As this will have effect on the UI, could help with a comparison. Can skip if not easy to reproduce the instance.

@spuru9 Thanks! This is a backend-only change and no UI/frontend code is touched. The user-visible effect is on the  /jobs/overview  data the UI renders: today, one incompatible archive causes the entire job list to go blank but after this fix, all other jobs render correctly and only the incompatible entry is skipped.