utils/update_mir_test_checks.py may cross machine function boundaries while parsing a *.mir test looking for registers: YAML-field a little too greedily than it actually needs. If there is a MF w/o registers: field followed by a MF with one it will parse both of them with the name of the first one, and registers and body of the second one and eventually crash.
This patch also adds a LIT-test for utils/update_mir_test_checks.py itself to ensure we don't regress on this or, frankly, anything else.
Is it necessary to check the stderr in this test?