Add label selector observability to placement group tables and actor and task detail pages

[alanwguo]

Why are these changes needed?

Follow-up to #53423

Missed a few places in the UI.
Also updates placement group tables to use the same code preview component as the actor and tasks tables.

Placement group table

Actor detail

Task detail

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 :(

[Copilot]

Pull Request Overview

This PR adds observability for label selectors across several UI components and updates the placement group tables to use a unified code preview component.

• Extend the Bundle type with an optional label_selector field.
• Add “Label Selector” sections in Task and Actor detail pages using CodeDialogButtonWithPreview.
• Introduce a LabelSelector column/component in the Placement Group table.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
python/ray/dashboard/client/src/type/placementGroup.ts	Add label_selector to Bundle type.
python/ray/dashboard/client/src/pages/task/TaskPage.tsx	Display label selector in task details.
python/ray/dashboard/client/src/pages/actor/ActorDetail.tsx	Display required resources and label selector.
python/ray/dashboard/client/src/components/PlacementGroupTable.tsx	Add LabelSelector component and table column.

[MengjinYan]

Thank for the quick turn-around! I'm not familiar with the UI code to review the exact change, but the change of dashboard UI looks good!

[alanwguo]

@MengjinYan ready to merge!

[MengjinYan]

@edoakes Can you help to merge the PR?

[bartcheers]

Looks great. Other than the waitFor vs setTimeout there's a small opportunity to DRY up undleResourceRequirements and LabelSelector since they share quite a bit of the logic, but they don't seem exactly the same so might be overdoing it.

[bartcheers]

You can do something like this with testing-library instead of the timeouts, which should make the test less flaky:

 await waitFor(() => {
      expect(screen.queryByText("pg-987654321")).not.toBeInTheDocument();
      expect(screen.queryByText("pg-555666777")).not.toBeInTheDocument();
    });

[bartcheers]

There 3 other places in this PR where you could replace setTimeout for waitFor