Different forms of log can't be easily correlated due to missing action/spawn identifier

### Description of the feature request:

Add RBE operation ID / action digest in timing profile

### Which category does this issue belong to?

Performance

### What underlying problem are you trying to solve with this feature?

This allows us to identify the root of slow action. Currently we have to do fuzzy matching based on target name and invocation ID.

### Which operating system are you running Bazel on?

_No response_

### What is the output of `bazel info release`?

_No response_

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse master; git rev-parse HEAD` ?

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Start by tracing where Bazel's timing profile is produced and where RBE action metadata is available; the issue specifically calls out the operation ID and action digest. Done means timing-profile entries expose that identifier so logs can be correlated without fuzzy matching by target name and invocation ID.

Written by the indexing model from the issue text.