Create and manage connected repositories with Terraform

Cloudsmith has recently rolled out a significant update to its Terraform provider, introducing the `cloudsmith_connected_repository` resource. This new capability empowers developers and operations teams to declare and manage their connected repository configurations as part of their infrastructure as code (IaC) practices. Historically, managing these connections might have required manual intervention or separate scripting, leading to potential inconsistencies and operational overhead. With this integration, users can now define connected repository settings alongside other Cloudsmith resources within their Terraform configurations. This allows for the application of changes through standard `terraform apply` workflows, bringing the benefits of version control, auditability, and automated deployment to the realm of package repository management. The feature is designed to support a broad spectrum of package formats, including popular ecosystems like Maven, Docker, Python, NPM, Go, Cargo (Rust), NuGet, Helm, Conda, and Conan. Beyond just defining connections, the update also includes practical improvements such as a new `npm upstream tags take precedence` setting. This allows upstream distribution tags (dist-tags) to override Cloudsmith's default semantic versioning-based tag assignment for npm packages, offering greater flexibility and alignment with external registries. By enabling the programmatic management of connected repositories, Cloudsmith aims to streamline the setup and maintenance of complex software supply chains, ensuring consistent, reproducible, and automated repository configurations across environments. This move further solidifies the role of Terraform in managing not just infrastructure, but also the critical components of software delivery pipelines.