Fix collection optimization to finalize VTables cleanup (Extraneous data removed: memory gain)

Remaining to be done
------------------------------

This nearly finalizes the new @StaticBindings implementation: It is functional, but some empty structures remain and cleanup algorithm (BasicInternalDataOptimizer) should take private data structures into account.

One more step could be to handle "_stubs" functions pointers to enable multi-instance support for @StaticBindings and remove the @Singleton-everywhere restriction.

Done
----------

The previous implementation had some code reminiscent of past times where we had exception cases every time we met a collection.

Here, when generating interface data for bindings destination side, if binding source was a collection, we tagged the server to tell it to keep its data since we didn't optimize collections.

Now this solution is irrelevant and led to residual useless data being written: We remove every "reverse-collection-binding-descriptor" exception section. Data gain is very sensible, as well as some effect on text section size.