When trying to follow an import, and failing a with a path relative to the current file, attempt to resolve the path relative to the current working directory
This solves a possible issue where the protobuf import statements are relative to a base path.
The current behaviour results in trying to import the wrong resolved path.
When trying to follow an import, and failing a with a path relative to the current file, attempt to resolve the path relative to the current working directory