Relative-navigated imports don't work in SolidityCompiler -- path variant

[3Nigma]

So if you start out with the following snippet:

var solc = require('solc');

var input = {
  language: 'Solidity',
  sources: {
    '_.sol': {
      content: 'import "../lib.sol"; contract Whatever { }'
    }
  }
};

function findImports(path) {
  console.log(`Import-resolution requested for path '${path}'`);
}

solc.compile(JSON.stringify(input), { import: findImports });

You would expect to see Import-resolution requested for path '../lib.sol' while, in actuality, you get Import-resolution requested for path 'lib.sol' logged.

It looks like the solidity-compiler is loosing track of relative navigation directives. We need to compensate for this in Strato. The remix ide code might give some hints on how they resolve this.

Note: This ticket deals with fixing the behavior of Contract.allFrom({ path }) (+ the newFrom variant). The { code } behavior will be handled by #117 .

[3Nigma]

Unfortunately we can't switch SolidityCompiler directly to @remix-project/remix-solidity because the remix code only works in browser contexts while Strato should also work in node-js contexts.

[3Nigma]

Including this ticket in the 0.8.1 milestone release since this will not require a bump on the rollup-plugin-hedera-js package.