Async monitoring console (LWC) over AsyncResult__c

[Mateusz7410]

Motivation

The framework already persists job outcomes in AsyncResult__c, but there is no
UI to inspect them. Today the only way to see async state is raw SOQL, a report,
or the standard Apex Jobs setup page (which knows nothing about our custom
job ids, retry history, or chain relationships). Operating the framework at scale
means a dev or admin has to hand-write queries to answer "what failed and why".

A built-in Lightning console over AsyncResult__c would make the framework
operable at a glance and is a strong, visible selling point.

Proposal

A Lightning app / tab backed by LWC, reading AsyncResult__c, with views that
mirror our own Status__c values:

• Overview – counts by status (Completed / Failed / Skipped / in-flight),
  simple last-24h trend.
• In-flight – jobs currently enqueued or running.
• Completed – recent successes with drill-down.
• Failed – failed jobs with exception message + RetryHistory__c.
• Skipped – jobs skipped by a dependsOn outcome.
• Filter by job class name, status, and date range.

Notes

• Read-only first cut. Re-driving failed jobs is tracked separately.
• Controller SOQL runs WITH USER_MODE; respect FLS on AsyncResult__c.
• Ships inside the package; read-only views need no new global API.

Acceptance criteria

• New LWC under force-app/main/default/lwc with an Apex controller.
• Jest tests covering loading / data / error branches for each view.
• Docs page under website/.