fix:builds the AMD64 architecture image explicitly and pushes to Airbyte's repo for suing it in Airbyte Cloud

[activescott]

This fixes the issue when trying to setup the destination in Airbyte cloud by explicitly building the amd64 image. I left it also building the arm64 image, but it only pushes am64 to airbytes repo.

We could push the ARM64 image for working with Airbyte OSS locally on arm macs, but this will require one of two approaches:

1. Tagging it separately (we could just put an-arm postfix on the version tag?
2. In theory we could push a multi-architecture image, but since Airbyte builds it separately from pushing and tagging it, we have to use some experimental features in docker wrt manifest.

Option 1 is the simplest if we care about this.

I also stopped pushing to the Glide-operated Image repo. While Airbyte told us to follow the OSS instructions which included using our own repo, when they enabled the custom docker connectors in Cloud - that ended up forcing us to use a docker image repo managed by them 🤦 So we could tear down that repo in gcloud and clean up the push script to clean this up further.

Let me know if you want me to make those changes or if you'd rather just run with this?

[chkn]

I think this is great for now! Probably not worth investing in the multi-arch stuff unless we have specific needs. We can always build the ARM64 image locally, or even just run the AMD64 image directly on Mac using Rosetta.