Relative paths not correctly resolved by 'using module' statement

[daviwil]

@AndrewGaspar identified this issue and filed a bug at the PowerShell/vscode-powershell repo:

PowerShell/vscode-powershell#64

We need to provide the proper working directory to the PowerShell parser when parsing each file so that module path resolution works correctly.

[daviwil]

I've got a fix for this but the build fails on AppVeyor because it isn't using the latest Windows/WMF release. I'll see if I can get someone to update the imagine this week so I can include this fix with the 0.4.0 release. Here's the branch where the fix is stored:

https://github.com/PowerShell/PowerShellEditorServices/tree/daviwil/using-module-fix

[daviwil]

I'm going to push this one out for 0.4.1 to give a little more time for getting the AppVeyor situation straightened out.

[daviwil]

Moving this ahead to 0.5.0 because WMF 5 RTM won't be out in time to have it installed on our AppVeyor image for 0.4.2 (VS Code 0.4.1)