Exclude benchmarks and fuzzing from default builds

[myrrc]

This PR adds default-members in Cargo.toml which exclude benchmarks and fuzzing
from the default build. This should have an impact on CI as well.

[AdamGS]

I'm not sure I agree with the first point, but the latter seems very reasonable, no reason to treat auxiliary code the same as the code crates.

[codspeed-hq]

Merging this PR will degrade performance by 17.99%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

❌ 6 regressed benchmarks
✅ 1520 untouched benchmarks
⏩ 10 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	chunked_bool_canonical_into[(1000, 10)]	20.4 µs	35.4 µs	-42.42%
❌	Simulation	chunked_varbinview_into_canonical[(1000, 10)]	176.8 µs	212.9 µs	-16.98%
❌	Simulation	chunked_varbinview_canonical_into[(100, 100)]	272.7 µs	307.9 µs	-11.41%
❌	Simulation	encode_varbin[(1000, 8)]	143.6 µs	160.6 µs	-10.61%
❌	Simulation	encode_varbin[(1000, 4)]	142.9 µs	159.9 µs	-10.61%
❌	Simulation	encode_varbin[(1000, 32)]	148.5 µs	165.2 µs	-10.09%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing myrrc/faster-ci-builds (862eff4) with develop (c6a0b7b)}

Footnotes

1. 10 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[AdamGS]

debug info is a feature of dev builds. If you don't want it, you can build the specific crates you care about or use ci profile.

Adam is right

[AdamGS]

you have a conflict in CI