About to push my first custom connector to "dev" and wondering what the best practice is here. Namely, I've developed the connector locally after pulling down Airbyte, and I can run it locally to my satisfaction from the UI. Now I have to get it to the Azure VM running Airbyte in my dev environment. A few questions there: 1. CI/CD, how do? Are other people copying and pasting from the folder the CLI created into a new folder and uploading just that to a Git repo? Is there a better developer experience than that? (presumably I'm not going to upload an entire fork of Airbyte) 2. Accessing the docker registry from a VM, how do? Namely simply logging in to azure from the VM running the containers doesn't work like it does locally, presumably because Airbyte is running in docker containers which aren't themselves logging into azure. Thanks!