unified: Add test with inheritance+nested classes

Inheritance and access to nested classes is one of the reasons not to apply the heuristic as a "fixup" after the recursive layer, because when a base class is resolved through the folder heuristic, access to nested members still need to be resolved through the standard logic.

Author: asgerf

unified/ql/test/library-tests/static-name-binding/not-a-package/Main/Drivers/Driver.swift

@@ -1,4 +1,5 @@
 class Driver { // name=Main.Driver
+    class Nested {} // name=Main.Driver.Nested
 }
 
 class UniqueToMain {}

unified/ql/test/library-tests/static-name-binding/not-a-package/Main/Runner.swift

@@ -1,5 +1,10 @@
 func main() {
     Driver(); // $ access=Main.Driver
+    Driver.Nested(); // $ access=Main.Driver access=Main.Driver.Nested
     UniqueToMain(); // $ access=UniqueToMain
     UniqueToMock(); // $ access=UniqueToMock
 }
+
+class MyDriver: Driver { // $ access=Main.Driver
+    class B: Nested {} // $ access=Main.Driver.Nested
+}

unified/ql/test/library-tests/static-name-binding/not-a-package/Mock/Drivers/Driver.swift

@@ -1,4 +1,5 @@
 class Driver { // name=Mock.Driver
+    class Nested {} // name=Mock.Driver.Nested
 }
 
 class UniqueToMock {}

unified/ql/test/library-tests/static-name-binding/not-a-package/Mock/Runner.swift

@@ -1,5 +1,10 @@
 func main() {
     Driver(); // $ access=Mock.Driver
+    Driver.Nested(); // $ access=Mock.Driver access=Mock.Driver.Nested
     UniqueToMain(); // $ access=UniqueToMain
     UniqueToMock(); // $ access=UniqueToMock
 }
+
+class MyDriver: Driver { // $ access=Mock.Driver
+    class B: Nested {} // $ access=Mock.Driver.Nested
+}