Wrong generated code when using import alias for Dart tables about drift

[simolus3]

Thanks for opening the issue, I actually wanted to fix this for a long time! In the writer, we only get a name of the element and its definition uri and we have to resolve its import alias based on that. It's not a fully sound solution, but most instances of this should be fixed by 261c151. That looks up all named imports in a library and picks the first one that matches. It's not correct because, if a name is imported both with and without a name, we won't always pick the right one now. But it's likely that most of these cases are already broken today, and this will at least improve some of them.

[davidmartos96]

Thanks Simon, as always! 😄