In-memory sizes of symbol semantic results are too large

[JonatanWaern]

This is mostly caused by ubiquitous and/or automatically set parameters (name, qname, etc.). In testing I have observed one of these having 4.5~gb of reference information associated with it, which is not tenable. For certain devices, this will crash the analysis outright depending on the running environment.

However, optimizing this is non-trivial, currently the information stored is a vector of heap-references to mutex-d symbols. So I think optimization on the size of each element is unlikely, instead we simply must store fewer elements somehow.

A side-effect of solving this is that (depending on the solution) we will also see analysis speed-ups, as currently much of the time is spent on moving these very large reference lists around.

[JonatanWaern]

At least partially fixed by #154, although further optimizations are most certainly possible

[JonatanWaern]

Moving to medium priority since usability has been restored by #154