🐛Docker image pulling: progress issues while pulling ti-postpro

[sanderegg]

What do these changes do?

ti-postpro:2.0.33 triggered some unforeseen issues in the docker pulling process due it seems to unexpected docker pulling status strings.
This PR shall ensure the process does not fail due to pydantic ValidationError but instead logs the issue so that it can be fixed later as this issue proved very hard to reproduce due to the sheer size of the involved docker image (it triggers timeouts while trying to reproduce in pytest, which is not the observed error).

For info: @Konohana0608

Related issue/s

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[codecov]

Codecov Report

Attention: Patch coverage is 85.29412% with 5 lines in your changes missing coverage. Please review.

Project coverage is 87.7%. Comparing base (cafbf96) to head (493e1eb).
Report is 363 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #6089      +/-   ##
=========================================
+ Coverage    84.5%   87.7%    +3.2%     
=========================================
  Files          10    1130    +1120     
  Lines         214   49363   +49149     
  Branches       25     748     +723     
=========================================
+ Hits          181   43335   +43154     
- Misses         23    5866    +5843     
- Partials       10     162     +152     

Flag	Coverage Δ
integrationtests	64.7% <ø> (?)
unittests	85.4% <85.2%> (+0.8%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...ges/service-library/src/servicelib/docker_utils.py	94.1% <85.2%> (ø)

... and 1139 files with indirect coverage changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud