Describe the bug
I'm trying to use importer.Import() in my own application, with the VerifyManifest option set to true.

importer.ReadManifest() appears to take the path to an .ovf file, gets the file from that path using filepath.Base(), then changes the extension of that file to .mf in order to find the manifest.

However, at no point is the absolute path added back onto the resulting filename, so the reads will be done relative to the current working directory of the application.

To Reproduce
Steps to reproduce the behavior:

1. Have your application set to a working directory different from where your OVF is stored.
2. Call Import with an absolute path to an OVF and VerifyManifest set to true.
3. The import will fail with an error saying it cannot find the file specified, with a relative path. For example:

error importing OVF application 'foo' from 'C:\\Users\\SomeUser\\AppData\\Local\\Temp\\foo_704290563\\foo.ovf': manifest %!q(<nil>): open foo.mf: The system cannot find the file specified.

Expected behavior
Manifest verification should succeed regardless of the current working directory of the application and where the manifest file is located.

Affected version
v0.43.0

Screenshots/Debug Output
N/A

Additional context
N/A