[CRE-739] retry proto registration

[Tofel]

---

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes enhance the reliability and functionality of Docker Compose tests and schema registration in a microservices-based framework. Specifically, the addition of retries in schema registration aims to address transient network issues, while the update in Docker Compose tests ensures a more robust and comprehensive testing environment, including changes to environment variable configuration and service checks.

What

• .github/workflows/framework-dockercompose-tests.yml
  • Added a new GitHub Actions workflow for running Docker Compose tests, including setting up environment variables, AWS credentials, and caching Go modules.
  • This workflow aims to automate testing of Docker Compose setups for the framework, ensuring that changes do not break existing functionality.
• framework/components/dockercompose/chip_ingress_set/chip_ingress.go
  • Modified the service wait conditions to include a new HTTP status check for the Red Panda Schema Registry, improving the reliability of service startup verification.
  • These changes ensure that dependent services are fully operational before proceeding with tests or deployments, enhancing stability.
• framework/components/dockercompose/chip_ingress_set/protos.go
  • Introduced retry logic with backoff for registering schema, addressing potential transient network issues or race conditions with the schema registry.
  • The retry mechanism improves the robustness of schema registration processes, particularly in distributed and dynamic testing environments.
• framework/components/dockercompose/go.mod and go.sum
  • Added github.com/avast/retry-go/v4 as a dependency, enabling the use of retry logic in schema registration.
  • This dependency is crucial for implementing the retry mechanism in schema registration, ensuring higher success rates in unstable network conditions.
• framework/examples/myproject/smoke_chip_ingress_test.go
  • Updated the test file by removing an unnecessary skip and environment variable setting, streamlining the test execution process.
  • The adjustments make the testing process more efficient and less prone to being skipped unintentionally, ensuring more consistent test coverage.