Add benchmarks to Rusk CI

[HDauven]

Summary

To get insight into how code changes impact the network, it would be beneficial to include benchmarks as part of our CI. This gives us a baseline to monitor relative impact.

Possible solution design or implementation

Add jobs for relevant cargo benchmarks in the Rusk CI.

This can be done by either executing the relevant cargo bench commands in the specific, relevant subfolders or by introducing a make bench command.

We can opt to make it a trigger-able action, on each push or on merging to main.

Criterion can generate full reports, it would be beneficial to publish these on execution.