Remove 'deno' builtin module

[kitsonk]

BREAKING CHANGE

This PR removes the builtin module "deno". Only the use of the namespace of Deno is supported.

[ry]

@kitsonk I'm still seeing Deno stuff twice in --types

> ./target/debug/deno --types | grep noColor
  export let noColor: boolean;
  export let noColor: boolean;

[kitsonk]

@ry Oops. Yeah. That was the other change I forgot. Will fix in a little bit.

[kitsonk]

@ry the build failure (https://travis-ci.com/denoland/deno/jobs/183238342#L1796) looks like some sort of intermittent CI stability issue versus a problem with this patch.

[ry]

@kitsonk from just above that in the build log -

Uncaught NotFound: Cannot resolve module "deno" from "/home/travis/build/denoland/deno/js/deps/https/deno.land/std/http/http_bench.ts"
    at DenoError (deno/js/errors.ts:22:5)
    at maybeError (deno/js/errors.ts:41:12)
    at maybeThrowError (deno/js/errors.ts:29:15)
    at sendSync (deno/js/dispatch.ts:67:5)
    at fetchModuleMetaData (deno/js/os.ts:80:19)
    at _resolveModule (deno/js/compiler.ts:250:38)
    at resolveModuleNames (deno/js/compiler.ts:480:35)
    at compilerHost.resolveModuleNames (deno/third_party/node_modules/typescript/lib/typescript.js:117517:138)
    at resolveModuleNamesWorker (deno/third_party/node_modules/typescript/lib/typescript.js:86226:127)
    at resolveModuleNamesReusingOldState (deno/third_party/node_modules/typescript/lib/typescript.js:86451:24)

I guess we need to land denoland/std#247 and upgrade std in deno. complete

[kitsonk]

cool... all clear now

[ry]

@kitsonk PTAL I've added a commit to remove the builtin logic from libdeno as well

[kitsonk]

@ry LGTM... I thought about doing that as well, but thought it was an ok feature that might be needed in the future, but that really seems unlikely, as if we decided the Deno namespace became too much to manage we would simply add other namespaces and if the use case did ever come up it could be added back in.

[ry]

@kitsonk I hesitated too - but I think we should remove now because

1. it's dead code, and dead code should be removed.
2. it's very complex and poorly implemented.
3. it makes the module system simpler - which is generally a good thing
   Glad to be rid of this baggage !

[ry]

LGTM