Set Spike execution limit to 2M steps across all verification runs.
Created by: zchamski
In order to prevent runaway executions of Spike, this PR sets an execution limit of 2 million cycles on all Spike executions triggered by the CVA6 DV scripts. The mechanism used is the new Spike cmdline option introduced in PR #1949.
Sullary of file changes:
- cva/sim/Makefile (spike_stepout): Set up Spike stepout option if caller supplied a step count limit. (spike): Invoke Spike with a 'stepout' limit option (possibly empty).
- cva6/sim/cva6.yaml (iss: spike): Set step limit of Spike runs to 2M. Add explanatory comments.