seesaw_crickit_test.py fails with Invalid touch pin

seesaw_crickit_test.py fails with a ValueError Invalid touch pin

This is not surprising as the code tries to use ss.touch_read with crickit "pins" range(4) - 0 to 3 (no pin mapping).
In the Crickit.Pinmap the touch "pins" are correctly defined as 4 to 7, so the touch_read fails with a ValueError.
How did this example ever work?

Start with seesaw_crickit_test.py and compare its ss.touch_read calls with the touch entries in Crickit.Pinmap. Run the example or its test to confirm the Invalid touch pin failure; done means the touch-pin checks use the mapped range and no longer raise ValueError.

Written by the indexing model from the issue text.