ci: build individual crates

### Problem:

Building the entire s2n-netbench workspace may result in different dependencies and features being enabled than building each crate individually. This can result in problems when publishing to crates.io, such as https://github.com/aws/s2n-netbench/pull/5

### Solution:

Add CI tasks to build each crate individually, similar to as was done in https://github.com/aws/s2n-quic/pull/1673

### Requirements / Acceptance Criteria:

If a dependency is used that causes an individual crate to be unbuildable, the CI task will fail

[//]: # (NOTE: If you believe this might be a security issue, please email aws-security@amazon.com instead of creating a GitHub issue. For more details, see the AWS Vulnerability Reporting Guide: https://aws.amazon.com/security/vulnerability-reporting/ )

Review the workspace configuration and existing CI tasks, then use the approach from s2n-quic PR #1673 as the reference. Identify every crate in the s2n-netbench workspace and verify that CI builds each one independently. Done means CI fails when a dependency or feature makes an individual crate unbuildable.

Written by the indexing model from the issue text.