Add cargo check for all features

[AkhilTThomas]

This PR adds cargo-hack to build each target with all the possible feature flags.
Addresses #120

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.58%. Comparing base (67fc220) to head (c344974).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #121   +/-   ##
=======================================
  Coverage   59.58%   59.58%           
=======================================
  Files          33       33           
  Lines       16071    16071           
=======================================
  Hits         9576     9576           
  Misses       6495     6495           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[AkhilTThomas]

Caught an issue in databroker-cli for --no-default-features
So it should address #120

[SebastianSchildt]

@CodiumAI-Agent /review

[QodoAI-Agent]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 120 - Fully compliant Fully compliant requirements: Ensure that the no-default feature (disabling TLS support) is built in CI. Detect breakage in the no-default feature build. Not compliant requirements: []

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Conditional Compilation The addition of the #[cfg(feature = "tls")] attribute to the get_ca_cert method may cause unexpected behavior if the feature flag is not properly managed or tested. Ensure this conditional compilation is correctly handled. #[cfg(feature = "tls")] pub fn get_ca_cert(&mut self) -> Option<String> { self.ca_cert.clone() } CI Feature Check The addition of cargo hack check --each-feature ensures feature flag testing, but it should be validated that all relevant features are being tested and no critical features are missed. - name: "Check each feature" working-directory: ${{github.workspace}} run: cargo hack check --each-feature

[SebastianSchildt]

It seems we run this for each platform in the build matrix, but I think we do nothing platform specific here, so maybe moving it out can save some time?

[SebastianSchildt]

Maybe in the (unit) test job?

[AkhilTThomas]

@SebastianSchildt This adds ~5m 12s runtime for the unit test action.

[SebastianSchildt]

Nice. Looking good. As for the runtime, this should also profit from the caching. We can come back if it gets too long/annoying

🏖️