Dockerize updates

[david-leifker]

• Update dockerize's golang version
• Normalize dockerize build across all images
• Added postgres-setup module (not used by default)
• Remove tar, vulnerability CVE-2022-48303

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[anshbansal]

Should we create a separate base image for all our images? It seems like we are re-building the same thing multiple times for no good reason. We only need to re-build this base image part when we are actually updating dockerize version. Or if we want to build this every time then we only need to do that once in the docker unified workflow if we move this out to a separate base image. This might also speed up our builds a bit.

[david-leifker]

For the dockerize binary, not worth it building a base image for just that. It takes a few seconds to build it and it will keep the golang version updated from upstream so we wouldn't have to manually detect a need for an update. It is locked to the major version of golang.