Test WF fusing

[Githubguy132010]

This pull request significantly restructures and consolidates the build and validation workflows for the project. The changes involve removing redundant workflows and creating a new unified workflow that handles multiple build and validation methods. The most important changes are summarized below:

Workflow Consolidation and Simplification:

• Removed Redundant Workflows: The build-check.yaml, build.yaml, and dockerfile-check.yaml workflows were removed to streamline the CI/CD process. [1] [2] [3]

• New Unified Workflow: Introduced a new validate-build.yaml workflow that consolidates the functionality of the removed workflows. This new workflow uses a matrix strategy to run different types of build and validation tests, ensuring a more efficient and organized CI/CD pipeline.

Key Features of the New Workflow:

• Matrix Strategy for Testing: The new workflow uses a matrix strategy to run both direct build and Dockerfile build methods, allowing for parallel execution and better test coverage.

• Common Setup Steps: Shared setup steps for both build methods, including environment setup and repository checkout, to reduce redundancy and maintain consistency.

• Build and Validation Steps: Separate steps for direct build and Dockerfile build methods, including dependency installation, ISO build, and validation checks. This ensures that both methods are thoroughly tested.

• Cleanup and Reporting: Added cleanup steps and status reporting to ensure that resources are properly managed and the build status is clearly communicated.