Fix -imports handling aliased imports in source mode

[mtoader]

In source mode, when generating a mock within the same package that uses names from a package that is imported with an alias, the generated mock should obey -imports properly and generate imports with the provided alias.

If the generated code is not using the same aliases as the main filed in a package the go compiler will still happily run but if you want ot use this package as a source in another package where you want to generate a mock, mock will fail because it will not know what to do with a package that is imported with two different names in a source package.

This patch fixes the generation by making -imports handling do a more correct thing.

It can be argued that the correct behavior is, by default use the the same package aliases as the ones in the source file, however that change looked way more invasive and i didn't see a good coverage of tests that would help me make sure the changes worked well.

This is what i found to be the least invasive fix for #166.

[CLAassistant]

All committers have signed the CLA.

[mtoader]

@JacobOaks can you help with #166 and this ?

[r-hang]

lgtm!

The net effect of this change will be that the gomock generated code should now follow the aliases specified by the -imports mapping. It does seem like this fixes a bug where definedImports is never looked-up by the full path that map is populated with.

[mtoader]

@r-hang merged master into. Now it needs some maintainer approval

[mtoader]

@r-hang I'm not that familiar with the reqs for the internal tests but i believe the latest commit might fix the tests. Can you approve the workflow run ?