📎 Move semantic model to scanner

[arendjr]

Description

Currently, our analyser operates in two phases: a syntax phase and a semantic phase. The idea is that rules that don't need the semantic model can operate in the syntax phase, while that same phase is also used for building the semantic model. Then a second pass is done where the semantic model can also be used.

However, we now have the scanner, which also does its own pass on the scanned files in order to build the dependency graph. This means we effectively have three passes now. What's more, to improve the dependency graph and allow for resolving imports to concrete declarations, we will need access to the semantic model in the scanner. The reason for this is that without semantic model, we cannot resolve the target for an export declared with export { foo }.

Of course, if we need to build the semantic model in the scanner, we would do best to persist it and run the analyser in a single phase afterwards.