Arctic: Linux: Workbench resize does not automatically carry over to new tests

**Summary**

If you resize the workbench before starting the recording of a new test, the next test to be started will not inherit the new workbench size+position.

**Workaround**

You need to "wiggle" the workbench to ensure its size + position are correct in the Test.json file.

Do this after test start but before ctrl-shift-z.

**Details**

If you don't wiggle the workbench after test start (for test 2) but before ctrl-shift-z, then all screenshots will be taken using the default workbench size and location.

For example, if you moved the workbench upwards for the previous test, then your next test will only take screenshots of the bottom of the worklbench, plus a section of the non-workbenched screen below.

This has the secondary effect of causing test failure on replay, as the screenshot in the recording (where the workbench does not cover the entire screenshot area) will not match the replay (where the workbench is recreated according to the Test.json file and now covers the entire screenshot area).

Reproduce the Linux Arctic workflow described in the issue, focusing on the workbench resize before starting a new test and the resulting Test.json contents. Check the test-start and screenshot/replay flow around ctrl-shift-z. Done means a resized workbench is carried into the new test without wiggling, and recorded screenshots match replay without the workaround.

Written by the indexing model from the issue text.