Copy dart2js source into pkg/compiler

Copy dart2js source into pkg/compiler

sdk/lib/_internal/compiler/compiler.dart => pkg/compiler/lib/compiler.dart
sdk/lib/_internal/compiler/implementation/* => pkg/compiler/lib/src/*
sdk/lib/_internal/compiler/samples/* => pkg/compiler/samples/*

This is part 1/3:

Part 1: https://codereview.chromium.org/687973002/
Part 2: https://codereview.chromium.org/686113002/
Part 3: https://codereview.chromium.org/692513002/

These CLs are based on r41258.

Committed through https://codereview.chromium.org/694353007/

[Johnni Winther, 2014-10-29 13:07:53]

johnniwinther@google.com changed reviewers:
+ ahe@google.com, floitsch@google.com, paulberry@google.com, ricow@chromium.org

[Paul Berry, 2014-10-29 13:28:07]

lgtm

[Paul Berry, 2014-10-29 13:31:34]

On 2014/10/29 13:28:07, Paul Berry wrote:
> lgtm

One question, though: is it a problem that there's already a package on
pub.dartlang.org called "compiler"?

[ahe, 2014-10-29 13:59:45]

Would it be possible to move the files instead of copying. This way, git will
handle most merges automatically.

The way it is done now, I'm pretty sure git will just complain that you have a
bunch of conflicts: local edits to a file that was deleted locally.

[Johnni Winther, 2014-10-29 14:19:53]

On 2014/10/29 13:31:34, Paul Berry wrote:
> On 2014/10/29 13:28:07, Paul Berry wrote:
> > lgtm
> 
> One question, though: is it a problem that there's already a package on
> http://pub.dartlang.org called "compiler"?

pkg/compiler is still a pseudo package, though less pseudo than before this
move, so where are not publishing ours nor depending on the existing package we
have no conflict.

[Johnni Winther, 2014-10-29 14:20:26]

On 2014/10/29 14:19:53, Johnni Winther wrote:
> On 2014/10/29 13:31:34, Paul Berry wrote:
> > On 2014/10/29 13:28:07, Paul Berry wrote:
> > > lgtm
> > 
> > One question, though: is it a problem that there's already a package on
> > http://pub.dartlang.org called "compiler"?
> 
> pkg/compiler is still a pseudo package, though less pseudo than before this
> move, so where are not publishing ours nor depending on the existing package
we
> have no conflict.

Will do.