Correct fully qualified global variable names

[vinistock]

Closes #128

I added a test to verify that all fully qualified names we generate are what we expect. All of them were already correct, with two exceptions:

• Attributes. We're not generating the methods related to attributes yet (proposal in Remember attributes as bitflags #471)
• Global variables. This is fixed in this PR and there's a slight caveat. I changed the fully qualified to be just the global variable name, but I kept the owner as Object. I believe this is fine for now, but we may want to revisit later. Global variables are accessible everywhere, so maybe for completion/go to definition algorithms, it will make more sense to place it in BasicObject? Or perhaps we need the magic <main>? I'll leave that to a dedicated PR

[vinistock]

• Correct fully qualified global variable names #486 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.