Be less specific in 'unresolved import' error patterns

To make sure different test set-ups (check-fast) don't cause the
tests to fail.

Author: marijnh

src/test/compile-fail/bad-expr-path.rs

@@ -1,4 +1,4 @@
-// error-pattern: unresolved name: a
+// error-pattern: unresolved name: m1::a
 
 mod m1 { }
 

src/test/compile-fail/bad-expr-path2.rs

@@ -1,4 +1,4 @@
-// error-pattern: unresolved name: a
+// error-pattern: unresolved name: m1::a
 
 mod m1 {
     mod a { }

src/test/compile-fail/bad-module.rs

@@ -1,4 +1,4 @@
-// error-pattern: unresolved import: vec
+// error-pattern: unresolved import
 import vec;
 
 fn main() { let foo = vec::len([]); }

src/test/compile-fail/import-from-missing.rs

@@ -1,4 +1,4 @@
-// error-pattern:unresolved import: eggs
+// error-pattern:unresolved import
 import spam::{ham, eggs};
 
 mod spam {

src/test/compile-fail/import.rs

@@ -1,4 +1,4 @@
-// error-pattern: unresolved import: baz
+// error-pattern: unresolved import
 import zed::bar;
 import zed::baz;
 mod zed {

src/test/compile-fail/import5.rs

@@ -1,4 +1,4 @@
-// error-pattern:unresolved import: foo
+// error-pattern:unresolved import
 
 mod m1 {
     fn foo() { log "foo"; }