Improve the service startup progress display

[SCA-ZMT]

Tasks

Preview Give feedback

1. make use of current size / total if available @jsaq007
2. fix frontend expectactions with states (see below) @jsaq007
3. show a progress (progressive spinning wheel, progress bar or even percentage display) @jsaq007
4. Service startup progress osparc-simcore#5666
   UI/UX +1
   
5. 🎨Progress bar: Add structured message in progress report osparc-simcore#5702
   a:dynamic-sidecar a:storage +2
   
6. 🎨Ensure pulling s4l returns smooth increment of progress (Part 1) osparc-simcore#5664
   a:dynamic-sidecar +1
   
7. 🎨Image pulling progress: use overall size (Part 2) osparc-simcore#5684
   a:services-library +1
   
8. 🎨Image pulling progress: pass current/total size (Part 3) osparc-simcore#5685
   a:autoscaling a:director-v2 a:dynamic-sidecar a:models-library a:services-library a:webserver +6
   

Eisbock

Preview Give feedback

1. "copying project" / "instantiating template" status bar UX improvements #1628
   +0
   

   
2. s4l-and-rocket-starting status bar (with the head) UX improvements #1627
   1 of 1
   +0
   

   
3. Bug: Copying/instantiating template progress broken on prod #1604 osparc-simcore#6209
   bug +1
   

[sanderegg]

High level view of dynamic service starting procedure

1. User adding a node in GUI
2. dynamic sidecar started (SIDECARS_PULLING: 0)
   1. autoscaling detects whether more machines are needed (CLUSTER_UP_SCALING: 0 ... 0.4 ... 1) (Optional, might go fast)
3. dynamic sidecar running (SIDECARS_PULLING: 1) -> CLUSTER_UP_SCALING is completed
4. dynamic sidecar pulls information in any order and in parallel (SERVICE_INPUTS_PULLING,SERVICE_OUTPUTS_PULLING, SERVICE_STATE_PULLING, SERVICE_IMAGES_PULLING) progress goes smoothly from 0 ..0.5...1
5. Ready, waiting for the actual service to come up (connect to service webserver)

[mrnicegyu11]

Re-Opening this for the Eisbock sprint, as instructed by Nik:

• Nik is happy with the dy-service startup progress bar(s)
• The "copying project" / "instantiating template" status bar needs UX improvements, it is too plain and unresponsive if copying takes >10s (talk to NC or DK for details) @odeimaiz @jsaq007
• The s4l-and-rocket-starting status bar (with the head) needs UX improvements, it is too plain and unresponsive if starting s4l takes >10s (talk to NC or DK for details) @ignapas @mguidon