Benchmark discovery should be agnostic to installation of benchmarked package

Currently, benchmark discovery requires that the benchmarked project is installed in the master's environment, since benchmark modules are likely to do things like `import project`.  This has consequences if the API of the project changes over time.

Unfortunately, I think this probably means a move to parsing Python code, rather than importing it.