Improve CMake option testing and validation in package builds

[patrick-stephens]

Problem

Currently, CMake options testing needs to be pushed into the build process for packages to ensure consistent configuration validation across all target distributions.

Background

As mentioned in PR #3, we need stricter cmake processes to remove "niggling 'missing SASL', etc. bugs" that are only found later in the development cycle.

Proposed Solution

• Integrate comprehensive CMake option testing into the package build process
• Add validation steps similar to the verify-config.sh script but for build-time configuration
• Ensure all expected features are properly enabled/disabled during package creation
• Run these tests within the container build environment

Acceptance Criteria

• CMake configuration validation runs during package builds
• Tests catch missing dependency issues early in build process
• Integration with existing CI/CD pipeline
• Documentation for developers on how to add new CMake option tests

Related

• PR: feat: add OpenSuse builds and fix up container builds #3 - feat: add OpenSuse builds and fix up container builds
• Related to the new testing/verify-config.sh validation approach

[patrick-stephens]

Fixed in #100