[Dashboard] Fix the filtering of the job_id in getTasks.

[liuxsh9]

Why are these changes needed?

The current method of passing the job_id while retrieving task information in the dashboard appears to be ineffective, resulting in fetching all task information every time, instead of the tasks associated with a specific job.

The proposed fix will improve the performance of the dashboard.

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

[anyscalesam]

This feels like a good P1 to me @rynewang PTAL.

[alanwguo]

@rkooo567 please merge!

[alanwguo]

@liuxsh9 , btw, please add the "go" label so all tests are run. Not just the "microcheck" tests which is a cheaper subset of tests.

[rynewang]

so url arg job_id did not work, or it's inefficient in implementation?

[liuxsh9]

@rynewang It did not work previously, not perform the expected filtering.

[liuxsh9]

@liuxsh9 , btw, please add the "go" label so all tests are run. Not just the "microcheck" tests which is a cheaper subset of tests.

That's very important! But I think I don't have the permission to adjust the label? Can @anyscalesam help me with that? Additionally, is there a way to better specify the testing scope when I submit a new pr?

[rynewang]

tag added. once it passed we can merge