Import Aliases

[otaviof]

Let's follow up on @SaschaSchwarze0's comment and make sure the imports are well organized.

Some inputs about the import alias were drafted during a 1-on-1:

• must not contain the resource version, therefore in a future refactoring we only need to touch the imports section
• must have a standard, for instance reusing import name parts
• must avoid colliding with other symbol names, like for instance "build" is too simple/short