[heft] feat: add lifecycle events for Heft tasks + phases

[aramissennyeydd]

Summary

Alternative to #5232 that exposes Operation lifecycle events directly instead of through a metrics interface.

Details

We're trying to measure the duration of specific Heft tasks similar to the duration of specific Rush phases. Specifically, I'm trying to understand the impact of migrating from Webpack to Rspack beyond manual benchmarking. This also opens up visibility into sync/blocking tasks and how to improve Heft parallelism.

How it was tested

Added new project that verified that output had the correct information,

 ---- build started ---- 
[lifecycle:example-lifecycle-plugin] --- build started ---
[build:clean] Deleted 0 files and 5 folders
[lifecycle:example-lifecycle-plugin] --- typescript started ---
[build:typescript] Using TypeScript version 5.8.2
[build:lint] Using ESLint version 8.57.0
[build:lint] Using TSLint version 5.20.1
[build:typescript] Copied 3 files and linked 0 files
[lifecycle:example-lifecycle-plugin] --- typescript finished in 1.25s ---
[lifecycle:example-lifecycle-plugin] --- lint started ---
[lifecycle:example-lifecycle-plugin] --- metadata-test started ---
[lifecycle:example-lifecycle-plugin] --- api-extractor started ---
[lifecycle:example-lifecycle-plugin] --- lint finished in 0.00s ---
[build:api-extractor] Using API Extractor version 7.52.8
[build:api-extractor] Analysis will use the bundled TypeScript version 5.8.2
[lifecycle:example-lifecycle-plugin] --- api-extractor finished in 0.61s ---
[lifecycle:example-lifecycle-plugin] --- metadata-test finished in 0.61s ---
 ---- build finished (1.878s) ---- 
-------------------- Finished (1.88s) --------------------

Impacted documentation

[dmichon-msft]

This is definitely getting really close. It feels a lot cleaner now than the initial approach and gets us closer to being able to converge the runner stacks between Rush and Heft.

[aramissennyeydd]

@dmichon-msft Should be ready for another round - basically updated the events to treat the phase operation more like a silent architectural node. It is no longer part of the input types to OperationExecutionManager, has no metadata, was already not being consumed by the beforeExecute/afterExecute hooks, but now gets explicitly skipped.

[dmichon-msft]

Little bit of cleanup left from old casts and type checks

[dmichon-msft]

Just a minor nit left, otherwise looks good.

[aramissennyeydd]

@dmichon-msft Updated 🙂

[aramissennyeydd]

@dmichon-msft Anything else that I need to do for this PR?

[dmichon-msft]

@aramissennyeydd , looking at this again since I'm doing some work on @rushstack/operation-graph; was it a deliberate choice to make these hooks Async or was that purely due to copying the existing hooks?

[aramissennyeydd]

@dmichon-msft I believe it was to copy the existing hooks, the plugin I wrote that uses this does all async work during recordMetrics or toolFinish.