[FLINK-40097][historyserver] Introduce Lazy Loading for HistoryServer

[chenzihao5]

What is the purpose of the change

Introduce a lazy-loading mode that loads archive details on demand, improving archive load times and enhancing the user experience.

Brief change log

• Introduce three configurations:
  • historyserver.archive.load.mode to specify the loading mode, supports EAGER(default) and LAZY
  • historyserver.lazy.fetch.executor.common.pool-size and historyserver.lazy.fetch.executor.individual.pool-size to control the loading thread pool
• Add PENDING, OVERVIEW_PARSING, OVERVIEW_CREATED, DETAIL_PARSING in ArchiveEventType.
• Support lazy-loading in org.apache.flink.runtime.webmonitor.history.AbstractHistoryServerHandler#loadResource.

Verifying this change

This change added tests and can be verified as follows:

• Added unit tests for lazy-loading mode, verify the different stages when lazy loading archive by BlockingArchiveStorage.
• Added unit tests for other functions that are included in this feature.

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? yes
• If yes, how is the feature documented? docs

---

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

• Yes (Claude-4.7-Opus 1M Context)

[flinkbot]

CI report:

• 62eb688 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[chenzihao5]

@reswqa Thanks for your review. I have updated the code after resolving the comments.

[reswqa]

Thanks for the update.