Only pull image on container create if the error matches

[LaurentGoderre]

- What I did

Validate that the image not found error matches the container definition before pulling it. This supports moby/moby#48798

- How I did it

Check the error message from the server before pulling.

- How to verify it

Unit tests are updated to demonstrate it.

- Description for the changelog

Validate that the image not found error matches the container definition before pulling it

- A picture of a cute animal (not mandatory but encouraged)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.66%. Comparing base (b462778) to head (6800e80).
Report is 11 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5743      +/-   ##
==========================================
+ Coverage   59.51%   59.66%   +0.15%     
==========================================
  Files         346      340       -6     
  Lines       29376    29127     -249     
==========================================
- Hits        17483    17379     -104     
+ Misses      10923    10784     -139     
+ Partials      970      964       -6     

[thaJeztah]

Hm... honestly, not sure if we should go down this road again, because string-matching is really brittle (we used to have this, and changing an error message between releases resulted in things failing). e.g. linters will complain that No such: should not be capitalised, and changing it to lower case (no such image) will break logic.

I think ideally, we'd look at some other options, which may be additional, structured, information in the error-response, or (something discussed in the past) even consider moving the pulling to the daemon side (although there will still be some work to do if the volume requires different authentication than the image that's being run)

[LaurentGoderre]

@thaJeztah I was debating changing the error message from the daemon to include a raw JSON representation of the error which would be a lot less brittle but wasn't sure if it was too big of a change