`docker run` dont support using new images just by restarting.
Containers need to be stopped, removed and started again to run on the new image.
Hence wont auto-update all containers, just their images and the user has to manually recreate each container.
- Added a way to choose from a numbered list what to update.
- Repairing some array-mistakes.
- Cleaned up some formatting and presentation.
- Set so that choosing -y or -n with flags wont give a numbered list.
- Edited options, auto-update through either -y or -a (yes or auto) with same result.
Moved where the `options` function got called, and replaced the "Containers with updates available:" -listing with the numbered list straight away.
Instead of having the question "want updates?" before listing with numbers.
Cleaner this way.
Choosing what containers to update was broken due to array mistakenly was a list.
Now fixed and should work fine, no matter what order specified eg. `5,1,2,7`
Changed the logic in comparing the digests - if the local check had multiple digests for an image, the old logic would be inaccurate.
New logic just check if the newest digest is among the list of local digests, should avoid some false positives.
Added error check so that instead of breaking, if containers cant be checked on the registry (eg. locally built or deprecated) they'll be added to a error-list.
Added the possibility to check multiple containers by name-wildcarding. Eg `dockcheck ng` would check all containers named anything with `ng` like nginx_local, reverse_nginx
