Import resolver should be capable of resolving also methods and constructors

[Akirathan]

ImportResolver is incapable of resolving symbols within from ... import symbol_1, symbol_2, ... statements. We should provide another compiler step to resolve these symbols, along with symbols from all import statements like from Module.Type import all (which should collect all the constructors), etc. The step should update BindingMap with the additional information.

There is an abandoned PR that adds this functionality - #6457. Before this PR will be integrated, we should think over the architecture of current BindingMap - it is currently modified in-place from many places, which is potentially dangerous, especially because BindingMap is serializable, and it is cached.

Related:

• Importing a nonexistent module/type using from syntax does not yield any errors #5936
• from/all import must not include module in name resolution #3931
• Fully Qualified Name reference not resolved correctly #6553
• ImportResolver should resolve transitively exported symbols #6669
• Imported name shadowed by local type not reported #8868

Tasks

Preview Give feedback

1. Enable/add all the tests from https://github.com/enso-org/enso/pull/6457/files#diff-de25bd229c75933a6fb950d1d00d8dfcca100058614c230de09c32aac7479816
2. Revert https://github.com/enso-org/enso/pull/6726/commits/5595728f39fd50b4aca845d7778415dd3ed09beb

[Akirathan]

This issue blocks #9692 (comment) - private check cannot throw a compiler error when accessing private constructors or private methods.