Fix module name when generating wrapper

[ArtemkaKun]

Before this PR, the module name was generated wrongly when generating a module for a single file, when the path to this file was relative

[spytheman]

Can you add a small test for that fix?

[ArtemkaKun]

Unfortunately, I have no time for now. I will do that asap

[ArtemkaKun]

@spytheman I'm not sure how to add a test for this. The problem existed when executing c2v wrapper command on a C file with a relative path. This PR makes sure the path of the file is always absolute. Since paths to test files in our test runner script are absolute, not sure if it is worth it to try to extend test runner code to test this particular case

[JalonSolov]

The test would be to translate a C file with just enough in it to show that this fix works, and use relative paths when translating.

[ArtemkaKun]

The test would be to translate a C file with just enough in it to show that this fix works, and use relative paths when translating.

The problem is that test runner script walks through every test file by abs path. I would need to somehow ignore one single file and convert its path to a relative. Not sure if adding this complication to test runner script will pay off

[JalonSolov]

Just generate the C file as part of your test. Don't make it a permanent file that's checked in.

[ArtemkaKun]

I implemented a trick to run tests for both absolute and relative paths, so this should cover this case as well