Cherry pick the OOM graph PR

[rkooo567]

Add the OOM failure graph.

I added under the top section (task/actor) since it is much easier to discover + related to tasks and actors failures.

In the long term, we can replace this graph to failure type graph (e.g., include application failure, node failure, etc.).

Why are these changes needed?

Related issue number

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[clarng]

approved per #33999 (review)

[clarng]

@rkooo567 shall we fix dco?

[rkooo567]

I think it is okay. Let me just merge it!