Separate class hierarchy calculation from class member semantics
fix Issue 12078 - forward reference issue with is() and curiously recurring template pattern
fix Issue 12143 - Base class is forward referenced
fix Issue 11622 - Assertion failure in totym(), glue.c, line 1288
[Refactoring] Move Type::reliesOnTident into a visitor class
[Refactoring] Simplify the role of inferType function

Move lambda deduction handling code from inferType to deduceType
[Refactoring] Add FuncExp::matchType and simplify lambda conversions
[Refactoring] inferType
Merge pull request #3473 from 9rnsr/refactor_deduce

[Refactoring] around lambda type deduction
Merge pull request #3384 from 9rnsr/refactor_aggregate

Issue 12078 & 12143 & 12555 & 11622 - Separate class hierarchy calculation from class member semantics
Fix issue 313 & 314

Points:

1. Most of import declarations will insert their fully qualified names in local symbol table.

Currently, it is stored only in one place - `Module::modules`. After this change, in addition to that,
each `ScopeDsymbol::symtab` will have the "local package tree" which represents the scope local imports.

For example:

```d
class C {
    import core.stdc.stdio;
    import core.stdc.stdlib : malloc;
    import core.stdc.stdlib : free;
    void func() {
        import core.stdc.string;
    }
}
```

`symtab` of class `C` and `C.func` will have following package object trees:

```
// in C
Package('core') <----------+
 + Package('stdc') <-------|--+
    + Import('stdio')      |  |
    + Import('stdlib')     |  |
        names = ["malloc"] |  |
  +---- overnext           |  |
  |                        |  |
  +-> Import('stdlib')     |  |
        names = ["free"]   |  |
                           |  |
// in C.func()             |  |
Package('core') aliassym --+  |
 + Package('stdc') aliassym -+
    + Import('string')
```

In there, `Import` object will be the leaf of the tree.
It's done by `Import::addPackage`.

2. A part of local package tree will be merged into other tree.

This example case of public import should work.

```d
module a;
public import std.stdio;
```
```d
module b;
import a;
import std.algorithm;
std.stdio.writeln();    // point
```

In module b, 'std.stdio' should be visible. To realize it, import declarations will pull
the fully qualified name of public imports in the imported module.
Finally, module b will have the package tree:

```d
Package('std')
 + Package('algorithm')
 + Package('stdio')   <--- Pulled from module a, by `import a;`
```

Same work is necessary on class inheritance. Public/protected imports in base class scope
should be pulled in the derived class scope.
Add test/compilable/testimport1.d
Add test/compilable/testimport2.d
Add test/compilable/testimport3.d
Add test/compilable/testimport4.d
fix Issue 313 - [module] Fully qualified names bypass private imports
fix Issue 314 - [module] Static, renamed, and selective imports are always public
Add test case for issue 12359 before deprecation
fix Issue 12359 - implicit overload merging with selective imports should be removed

Show deprecation message for the implicitly merged overload set, by using cross-module overload set mechanism.