refactor(ci): Centralize Docker configuration testing using matrix strategy

[gustavovalverde]

Motivation

This PR addresses the need for Docker configuration testing identified in issue #9037. Our current testing approach for Docker configurations has several limitations:

1. Scattered Test Logic: Tests are duplicated across CI and CD pipelines, making maintenance difficult
2. Limited Coverage: Only a few basic configuration scenarios are tested
3. Scalability Issues: Adding new test scenarios requires changes in multiple files
4. Inconsistent Testing: CI and CD environments may diverge in their testing coverage
5. Difficult Integration Testing: Testing interactions with third-party applications is challenging

Depends-On: #9344
Closes: #9037

Solution

This PR implements a centralized, matrix-based approach to Docker configuration testing:

1. Architectural Decision Record (ADR): Created a new ADR documenting the rationale for centralizing Docker tests
2. Matrix Strategy: Converted multiple separate test jobs into a single comprehensive matrix-based test
3. Consolidated Test Scenarios: Moved all test scenarios from both CI and CD pipelines into a single reusable workflow
4. Expanded Test Coverage: Defined an extensive test matrix covering:
   • Network configurations (Mainnet/Testnet)
   • RPC server configurations (ports, listen addresses)
   • Directory and permission testing
   • Feature-specific configurations (Prometheus, tracing)
   • Mining configurations
   • Config precedence and generation testing
5. Simplified Workflow Interface: Reduced required inputs to just the Docker image identifier

This centralized approach makes it easier to add new test scenarios, including those that validate third-party integrations.

Tests

The solution is self-testing (validation of the test outputs must be done)

Specifications & References

• GitHub Actions Matrix Strategy: https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs

Follow-up Work

Future enhancements to consider:

• Add more complex integration tests with lightwalletd and other third-party applications
• Implement Docker Bake for local testing of complex build configurations
• Create testing scenarios for volume mounts and persistent data

PR Checklist

• The PR name is suitable for the release notes.
• The solution is tested.
• The documentation is up to date.
• The PR has a priority label.
• If the PR shouldn't be in the release notes, it has the C-exclude-from-changelog label.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 ⛓️ Depends-On Requirements

This rule is failing.

Requirement based on the presence of Depends-On in the body of the pull request

• depends-on = ZcashFoundation/zebra#9344 [⛓️ refactor(docker): Enhance Zebra configuration options and entrypoint logic #9344]

[upbqdn]

This is amazing.

[mergify]

⚠️ The sha of the head commit of this PR conflicts with #9423. Mergify cannot evaluate rules on this PR. ⚠️