CI does not exercise the MMQA test suite

[rptb1]

The problems in issue MMQA test cases fail on xca6ll would likely have been discovered much sooner if the MMQA tests were run by CI.

We should investigate this possibility.

[rptb1]

To measure resource usage, I ran:

rb@plover:~/git/mps$ time make -C code -f lii6gc.gmk clean testci testpollnone testmmqa
...
real	5m20,086s
user	4m29,833s
sys	0m47,138s

It seems quite likely we could incorporate this into our CI builds.

(Plover is a Steam Deck running Ubuntu 22.)

[gareth-rees]

The issue description says that "the problems in #84 would likely have been discovered much sooner" but that seems unlikely because the MMQA test suite did not run at all until #75 was (mostly) fixed. I made #82 on 2022-12-22 and #84 on 2022-12-25 so we could have learned about the failures at most three days sooner.

[rptb1]

We should consider whether it's feasible to run the MMQA test suite with deep checking. See #209 .