Add git_clone_strategy to repository acceptance tests

Tests that create repositories via deploy key were missing the
git_clone_strategy field, causing null constraint violations in
staging when dbt Cloud validates the field on save.

Generated with Claude Code

Author: donaghh

pkg/framework/objects/project_repository/resource_acceptance_test.go

@@ -68,6 +68,7 @@ resource "dbtcloud_project" "test_project" {
 resource "dbtcloud_repository" "test_repository" {
   remote_url = "%s"
   project_id = dbtcloud_project.test_project.id
+  git_clone_strategy = "deploy_key"
   depends_on = [dbtcloud_project.test_project]
 }
 
@@ -87,6 +88,7 @@ resource "dbtcloud_project" "test_project" {
 resource "dbtcloud_repository" "test_repository" {
   remote_url = "%s"
   project_id = dbtcloud_project.test_project.id
+  git_clone_strategy = "deploy_key"
   depends_on = [dbtcloud_project.test_project]
 }
 `, projectName, repoUrlGithub)

pkg/framework/objects/repository/data_source_acceptance_test.go

@@ -42,6 +42,7 @@ func repositoryDataSourceConfig(projectName, repositoryUrl string) string {
     resource "dbtcloud_repository" "test_repository" {
         project_id = dbtcloud_project.test_project.id
         remote_url = "%s"
+        git_clone_strategy = "deploy_key"
         is_active = true
         depends_on = [
             dbtcloud_project.test_project