[UX] Show 0.25 on controller queue

[Michaelvll]

Previously for controller process on the sky queue sky-jobs-controller-<hash>, we are showing CPU:8 as the resources, it is a bit confusing for how many jobs can be run in parallel. This PR makes it CPU:0.25 instead.

See job ID 10 (new) vs job ID 9 (old)

$ sky queue sky-jobs-controller-a37461fd 
Fetching and parsing job queue...

Job queue of cluster sky-jobs-controller-a37461fd
ID  NAME                         SUBMITTED    STARTED      DURATION    RESOURCES     STATUS     LOG                                        
10  test                         39 secs ago  34 secs ago  34s         1x[CPU:0.25]  RUNNING    ~/sky_logs/sky-2024-10-31-18-18-15-660126  
9   test                         5 mins ago   5 mins ago   1m 24s      1x[CPU:8.0]   SUCCEEDED  ~/sky_logs/sky-2024-10-31-18-12-39-221597  

Tested (run the relevant ones):

• Code formatting: bash format.sh
• Any manual or new tests for this PR (please specify below)
• All smoke tests: pytest tests/test_smoke.py
• Relevant individual smoke tests: pytest tests/test_smoke.py::test_fill_in_the_name
• Backward compatibility tests: conda deactivate; bash -i tests/backward_compatibility_tests.sh

[romilbhardwaj]

Hmm, so does RESOURCES now mean the RESOURCES consumed on the controller, and not the actual CPUs required by the job?

E..g., if I run sky jobs launch --cpus 16 -- echo hi, will it show 1x[CPU:0.25] in sky jobs queue?

[Michaelvll]

Hmm, so does RESOURCES now mean the RESOURCES consumed on the controller, and not the actual CPUs required by the job?

E..g., if I run sky jobs launch --cpus 16 -- echo hi, will it show 1x[CPU:0.25] in sky jobs queue?

sky jobs queue should show the exact resources required by a job. This change only affect the sky queue sky-jobs-controller- which should not be run most of the time by a user.