Add CI checks for wasm32 builds and feature flag correctness

[Jiloc]

We recently added official support for the wasm32-unknown-unknown target in stacks-common, clarity-serialization and clarity, but there's currently no CI check to ensure it stays working. Separately, PR #6228 revealed that some feature flags were broken without anyone noticing. These issues are easy to miss without dedicated CI checks.

Add a CI workflow that uses cargo hack to check all feature flags individually and ensure that wasm32 builds don’t regress.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.