A timing test that no longer fails on slower CI runners

The Build on main kept failing on a test that guards against the server freezing while many cards land in a row. It used a fixed limit of 500 ms of CPU time, which GitHub's slower runners kept crossing even though nothing was wrong. The test now measures that work against a rebuild of the canvas view on the same machine, so it still catches the real regression on any hardware without failing on a slow one.