Avoid hole bindings in unification solutions

We assume elsewhere that a hole binding only appears once, and these
aren't really solutions. The addresses #1242 (although the code there
still doesn't type check for a different type class resolution reason).
Can't assume explicit names in updateSolved

Fixes #1242