Capture some more sample programs from issue chapel-lang#11262

Bryant pointed out that the behavior of these tests has varied
over the past few releases/months which motivated me to capture
them to make sure further variation doesn't happen unexpectedly
(I believe the current behavior is correct, or at least, as
currently intended).

test/modules/use/topLevel/subVsTop.chpl

@@ -0,0 +1,15 @@
+module M {
+  module N {
+    proc fn() { writeln("M"); }
+  }
+}
+
+module N {
+  proc fn() { writeln("g"); }
+}
+
+{
+  use N only;
+  use M;
+  N.fn();
+}

test/modules/use/topLevel/subVsTop.good

@@ -0,0 +1 @@
+M

test/modules/use/topLevel/subVsTop1a.chpl

@@ -0,0 +1,15 @@
+module M {
+  module N {
+    proc fn() { writeln("M"); }
+  }
+}
+
+module N {
+  proc fn() { writeln("g"); }
+}
+
+{
+  use M;
+  use N only;
+  N.fn();
+}

test/modules/use/topLevel/subVsTop1a.good

@@ -0,0 +1 @@
+M

test/modules/use/topLevel/subVsTop2.chpl

@@ -0,0 +1,15 @@
+module M {
+  module N {
+    var x = 100;
+  }
+}
+
+module N {
+  var x = 42;
+}
+
+{
+  use N only;
+  use M;
+  writeln(N.x);
+}

test/modules/use/topLevel/subVsTop2.good

@@ -0,0 +1 @@
+100

test/modules/use/topLevel/subVsTop2a.chpl

@@ -0,0 +1,15 @@
+module M {
+  module N {
+    var x = 100;
+  }
+}
+
+module N {
+  var x = 42;
+}
+
+{
+  use M;
+  use N only;
+  writeln(N.x);
+}

test/modules/use/topLevel/subVsTop2a.good

@@ -0,0 +1 @@
+100

test/modules/use/topLevel/subVsTop3.chpl

@@ -0,0 +1,16 @@
+module M {
+  module N {
+    var x = 100;
+  }
+}
+
+module N {
+  var x = 42;
+}
+
+{
+  use M only N as N2;
+  use N only;
+  writeln(N.x);
+  writeln(N2.x);
+}

test/modules/use/topLevel/subVsTop3.good

@@ -0,0 +1,2 @@
+42
+100