Bump container image versions to v0.16.0 in quickstart

[vpavlin]

closes #1667

[LNSD]

Hi @vpavlin, I think we should have a latest tag for the image, which should be updated when a new container image is released. With that, we can avoid updating the README.md with every new version.

cc @jm-clius

[vpavlin]

The latest tag is currently over a year old:) So if we can fix it to point to the latest release, we can absolutely use that.

We should mention in the quickstart that using latest in production is a bad practice since you would potentially lose control of when and how to update in case the latest image is retagged.

[jm-clius]

Thanks for this! I agree that we could use latest here, though this is an example on how to use a specific release. I don't necessarily think we need to update it every time, though it's good that it's not way too old.

[LNSD]

LGTM ✅

We can merge it as it is, and when we do the next release, we generate the latest tag and update this one last time :)