feat(resources): add Bitbucket Data Center DevOps Platform Integration

[ryancurrah]

Add support for Bitbucket Data Center (Server) DevOps Platform Integration with SonarQube:

Note: Some files were modified/formatted by go fmt.

• Add sonarqube_alm_bitbucket resource for managing Bitbucket DevOps Platform settings
• Add sonarqube_bitbucket_binding resource for binding projects to Bitbucket repos
• Add sonarqube_alm_bitbucket data source for querying existing configurations
• Update GetBinding struct to include slug field for Bitbucket support
• Add example configurations in examples/ directory
• Generate documentation for new resources and data sources

The implementation follows the same patterns as existing GitLab and GitHub DevOps Platform Integrations. Bitbucket bindings are not supported in Community edition.

API endpoints implemented:

• POST /api/alm_settings/create_bitbucket
• POST /api/alm_settings/update_bitbucket
• POST /api/alm_settings/set_bitbucket_binding
• GET /api/alm_settings/get_binding
• POST /api/alm_settings/delete_binding
• POST /api/alm_settings/delete

Testing performed:

• terraform apply: successfully created Bitbucket DevOps Platform setting and project binding
• terraform apply (idempotency): no changes detected, resources remained stable
• terraform destroy: successfully removed all resources

[ryancurrah]

Looks like this is used by multiple resources GitLab, GitHub and now Bitbucket.

[ryancurrah]

To try and address the docker-compose flakiness I used ElasticSearches official docker-compose file to improve this one. If it does not work I will revert it.

https://github.com/elastic/elasticsearch/blob/main/docs/reference/setup/install/docker/docker-compose.yml

EDIT:

I removed those modifications. Looks like wget was removed from the search container and they switched to curl in their healthchecks SonarSource/docker-sonarqube@bc05dcd.

[ryancurrah]

😢 looks like we got rate limited or something from dockerhub. Maybe retry?

search-2 Error Head "https://registry-1.docker.io/v2/library/sonarqube/manifests/datacenter-search": toomanyrequests: too many failed login attempts for username or IP address

Starting sonarqube service container
  /usr/bin/docker pull sonarqube:lts-community
  Error response from daemon: Head "https://registry-1.docker.io/v2/library/sonarqube/manifests/lts-community": unauthorized: incorrect username or password
  Warning: Docker pull failed with exit code 1, back off 1.009 seconds before retry.

[ryancurrah]

The build is failing because the lts-datacenter tag hasn't been updated in seven months, while the standard datacenter tag was updated yesterday. Crucially, the old tag contains wget but lacks curl, whereas the new tag has curl but lacks wget. Until the LTS tag is refreshed, we need a health check script compatible with both utilities.