cloud-availability-updater: implement git interactions

[alafanechere]

What

Starts the work on https://github.com/airbytehq/airbyte-cloud/issues/4213
We want to automatically open PRs when a connectors becomes eligible to cloud.
This PR focuses on git interaction logics. PR creation and actual call to the new deploy_new_connector_to_cloud_repo will be done in future PRs.

Prior work:

• qa-engine: define cloud eligibility #21961 allows to fech a list of connectors eligible to Cloud

Future works:

• Finish https://github.com/airbytehq/airbyte-cloud/issues/4213 by automatically creating PRs
• Define new GitHub Action workflow on airbyte-cloud to run the Cloud Availability updater daily. (cf Cloud Availability Updater: bootstrap it  #21918)

How

Implement the logic to:

• add a connector to the Airbyte-cloud repo definitions mask
• locally regenerate the cloud catalog
• commit / push in a new branch on airbyte-cloud repo

Recommended reading order

airbyte/tools/ci_connector_ops/ci_connector_ops/qa_engine/cloud_availability_updater.py

Line 24 in 18abf99

def clone_airbyte_cloud_repo(local_repo_path: Path) -> git.Repo:

airbyte/tools/ci_connector_ops/tests/test_qa_engine/test_cloud_availability_updater.py

Line 43 in 18abf99

def test_get_definitions_mask_path(checkout_master, dummy_repo_path: Path):

🚨 User Impact 🚨

None, the code implemented is not actually called at the moment.

[github-actions]

Airbyte Code Coverage

There is no coverage information present for the Files changed

Total Project Coverage	24%	❌

[evantahler]

I love code that writes code!
Are there any special permissions you will need to run this on GH actions?

[evantahler]

I don't think I understand how this will have all the YAML properties form the OSS repo

[alafanechere]

We only need the connector definition id to add it to the mask.
But we usually comment the name of the connector . e.g

[evantahler]

Got it! We should add a note in the PR that this creates then about "...and if you you want to modify the connector (e.g. resourceRequirements) do so before merging this PR"

[evantahler]

👍 connector names shouldn't have any spaces or special chars

[alafanechere]

Are there any special permissions you will need to run this on GH actions?
I expect the Octavia PAT to have these super permissions. It's used in this workflow that commits to master...
If not I'll ask @supertopher 😄

[supertopher]

@alafanechere as long as you can commit code you can access secrets which is the only real barrier to GH actions.

they keys mostly have the same permissions, but there are some edge cases

I think most keys are basically users. there are a couple that own the org. If you see a permissions error I think the error message is pretty clear