move coerce_match{,_calls} and related tests into run-pass-valgrind

[pnkfelix]

Put (copies of?) coerce_match{,_calls} and related tests into run-pass-valgrind. Because our current testing infrastructure is not aggressive enough in checking that tests like this are actually behaving in a sound manner.

spawned off of: #20055 (comment)

(I did not attempt this in PR #21692 because I wanted to expedite landing the fix for the trans bug.)

[pnkfelix]

@nick29581 clarified the situation to me: even if valgrind is not available on a host, the tests in run-pass-valgrind will be run (just without valgrind checking them).

So resolving this is probably just a matter of moving the tests over.

(having said that, I am wary of the risk of injecting usage of valgrind will cause a PR to be inadvertently blocked, and thus I still want to wait to fix this until after PR #21692 lands.)

[steveklabnik]

Triage: it looks like these two tests are not yet in src/test/run-pass-valgrind/. This should be easy to do, though which tests exactly are "related" isn't quite clear to me.

[brson]

Triage: no news.