Parallelise and merge ci jobs, make sure rust dependencies are shared everywhere

[robert3005]

Leverage github's parallel steps to speed up our CI, merge steps where majority
of time was compilation

[codspeed]

Merging this PR will regress 1 benchmark

⚠️ 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

⚡ 4 improved benchmarks
❌ 1 regressed benchmark
✅ 2193 untouched benchmarks
⏩ 218 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	WallTime	arrow_checked_add_u32_neon[16384]	13.5 µs	20.3 µs	-33.35%
⚡	Simulation	decompress[u64, (4000, 1024)]	86.8 µs	71.5 µs	+21.37%
⚡	WallTime	arrow_checked_add_u32_avx2[16384]	21.4 µs	17.7 µs	+20.99%
⚡	Simulation	allocate_drop_arrow[0]	456.9 ns	402.7 ns	+13.45%
⚡	WallTime	mul_u32_nonnull_avx512	6.3 µs	5.6 µs	+11.66%

Tip

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

---

_{Comparing rk/parallelci (3120e65) with develop (3e2b65c)}

Footnotes

1. 218 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. ↩

[joseph-isaacs]

Why are there new benchmarks?

[robert3005]

Probably because they're in between merge base of this pr and develop. If we rebase they should go away

[AdamGS]

LGTM