Rework referrer logic to be independent of traceur directory structure.

The overall output of the compiler in multi-file mode is to create a set of
modules in an output file with names beginning with a versioned package name.
The referrer option is encoding both the package name and the path to the
output file from the root of the package directory. EG traceur@0.0.67/bin.
The source is relative to the output directory (eg ../src/Compiler.js).
The referrer causes these relative names to normalize to package names,
eg traceur@0.0.67/src/Compiler. In locate() we map these names back to
the file system using the uncommon part of the referrer and the output
directory (which is the baseURL).

The module names remain unchanged. The referrer now requires a path
and the internal logic that added a traceur-specific path is removed.

Review URL: https://api.github.com/repos/google/traceur-compiler/issues/1419

Closes #1419.
Fixup build after npm publish.

The Makefile used the wrong referrer for one step
and the bug was not evident until I published and
use the node_modules version to self-compile.

TBR=@arv

Review URL: https://github.com/google/traceur-compiler/pull/1421

Closes #1421.
Manual update version 0.0.68

Review URL: https://api.github.com/repos/google/traceur-compiler/issues/1422

Closes #1422.
0.0.69 on npm has no /bin.

Update to skip 0.0.69.

TBR=@arv

Review URL: https://api.github.com/repos/google/traceur-compiler/issues/1423

Closes #1423.
0.0.71
0.0.72
Update super to match latest spec.

`super()` now means call the proto of the current function.

Therefore we now need to be explicit with `super.method()`.