Generate cascading switch statements when number of bindings is large

[Jeffset]

Yatagan, as Dagger in fastInit uses "switching providers" mechanism to reduce classloading. This means that for every binding, that can't be created inline (has Lazy/Provider usages) there's an index assigned. And every provider/lazy object instantiates the binding using the index and a lookup (switch) table.

Now, the hypothesis is, that when the lookup table becomes very large, the performance is going to be penalized. Yatagan currently generates plain switch statement, while Dagger did so with only up to 100 objects, after that it generated another switch level with index % 100 labels.

Let's try to investigate and possibly introduce the optimization.

Might be reasonable to do when the performance testing is implemented in #7